Hane Platform
Key concepts
A one-page map of the main concepts in Hane Platform — organizations, definitions, business data, workflows, tasks, agents, documents, events, and audit.
This page lists the main concepts of Hane Platform with short definitions, shows how they relate, and points to the pages that explain each in detail. For finer distinctions between terms, see the glossary.
The map
Section titled “The map”Organization ├─ Members and groups (with roles) └─ Project └─ Environment (dev, stage, prod) ├─ Service accounts and API keys ├─ Active release (ReleaseBundle) ← manifests (definitions) │ types, rules, workflows, schedules, assignment rules, DeciderPolicies, agents ... └─ Business state records and relations ─ cases ─ tasks AgentRuns ─ ActionRequests (operations awaiting approval) documents and conversations events ─▶ event subscriptions (webhooks) └─▶ audit recordsOrganizations and access
Section titled “Organizations and access”| Concept | Meaning | Details |
|---|---|---|
| Organization | The unit that contracts with Hane. Data and permissions are separated here | Organizations, projects, and environments |
| Project | The unit within an organization that separates definitions and data. Create one per business app or purpose | Same |
| Environment | Development, staging, and production of the same project (dev, stage, prod). Data and credentials are separated per environment |
Same |
| Members and roles | Users who belong to an organization. The roles owner, admin, developer, operator, and viewer determine what they can do (scopes) |
Same |
| Service accounts and API keys | Non-human callers (your app’s server or CI) and their credentials. Bound to one environment of one project | Same |
| Suspension | An operation that stops all APIs and executions of an organization. Only an owner can lift it | Same |
Definitions
Section titled “Definitions”| Concept | Meaning | Details |
|---|---|---|
| Manifest | A YAML definition kept in Git, with apiVersion, kind, metadata, and spec |
Managing definitions as code |
| Definition | Something that is activated together with others (types, rules, workflows, agents, and so on). Bundled into a ReleaseBundle | Same |
| Setting | Something not bundled that takes effect as soon as it is applied (EnvironmentBinding, RoleBinding, and so on) | Same |
| Draft | A definition that has been applied but is not active yet | Same |
| ReleaseBundle | A set of definition revisions. Its content never changes | Same |
| Active release | The ReleaseBundle currently running in an environment (active_release) |
Same |
Business data
Section titled “Business data”| Concept | Meaning | Details |
|---|---|---|
| Types and fields | The kind of a record (vehicle, contract, and so on) and the names of the values a type has. Defined with Schema and Ontology manifests |
Business data |
| Record | One item of business data that follows a type | Same |
| Value state and source | How far a value has been verified (confirmed, estimated, pending inquiry, unknown) and where it came from | Same |
| Relation | A link between two records. Can have a validity period | Same |
How work proceeds
Section titled “How work proceeds”| Concept | Meaning | Details |
|---|---|---|
| Workflow | The definition of how a case proceeds, step by step | Workflows and cases |
| Case | One piece of work driven by a workflow. It has a subject record and the ReleaseBundle it started with | Same |
| Wait | A state of waiting for a task to complete, an event, the result of an approval, and so on | Same |
| Schedule | A definition that, at a set time every day, starts cases, runs an agent once, or starts one import from an external connection | Same |
| Task | One decision or piece of work for a person. Assigned to a group or a person, and closed with one of the defined outcomes | Approvals and tasks |
| Approval | A decider deciding to approve or reject the content of an operation with an external effect (the approval subject) | Same |
| DeciderPolicy | A definition that sets who decides, and the approval stages, per kind of operation and condition (amount, recipient) | Same |
Agents
Section titled “Agents”| Concept | Meaning | Details |
|---|---|---|
| Agent | An AI agent defined with its goal, input and output types, the tools it may use, and limits | Agents |
| AgentRun | One run of an agent. Records the tool calls, their results, and usage | Same |
| ActionRequest | An operation with an external effect proposed by an agent. It runs after approval, and the result is kept in the execution ledger | Same |
| Conversation | An exchange in which a user asks the chat agent for something in natural language | Built-in chat |
Documents, events, and audit
Section titled “Documents, events, and audit”| Concept | Meaning | Details |
|---|---|---|
| Document | An original file and its versions. Used for full-text search and for extracting field values | Documents |
| Extracted fact | A value read from a document that no person has verified yet. Once verified, it becomes a confirmed value in business data | Same |
| Event | A record of a change in a service (a case completed, a task created, a record updated, and so on) | Webhooks |
| Event subscription | A registration of the endpoint and event types to deliver to your systems as webhooks | Same |
| Audit record | A record of who did what under which permissions, chained to the hash of the previous record | Audit and usage |
Read next
Section titled “Read next”Organizations, projects, and environmentsMembers, roles, API keys, and invitations
Managing definitions as codeFrom manifest to activation
GlossaryWhat each term means and how terms differ