Kinds of consequential work, and what must be able to refuse them.
The schema, the seed catalog, the 216 published Mission Join work types from the 225-entry working catalog, what is not a work type, the rules that relate work types to offers and status, and the offer map.
- OTCS-0017 Work TypesDRAFT · in deliberation · earliest decision 2026-11-28
- OTCS-0017 seed drafts and batch 1, parked on main, not ratified
- The verb library
Acequia, Inc. is an invented organization. These pages present a working design, not deployment results; its contracted stages and change freezes are illustrative. The sections below mirror the Governed Autonomy workbook (v0.50): its columns, rules, invariants and catalogs, as written, with the worked example's organization named as it is there. The deployment's own rows, parties, contract identifiers and configuration stay with the deployment; where a table's rows stay, its columns are shown.
01Seed work types (UNRULED draft)workbook tab 09 · Work types
What this is for. The kinds of work a person or machine can do on the case, and what must be able to refuse each one.
A product name is not a kind of work. One product can do several kinds of work. How to use it. Find the kind of work. Read its ceiling, its reach, and who can say no.
Catalog version: draft 2026-10-07 (UNRULED). IDs are written object.verb. A names a kind of work and what must be able to refuse it. It never marks work as allowed. Each field is a catalog draft or a workbook draft awaiting a catalog ruling.
1. Work types — work types draft 2026-10-07 (UNRULED)
- ¶detection.triageTriage a finding
14 fields
- Object class
- detection
- Maps to
- read
- Roles (configurator · executor · verifier)
- Configurator: SOC lead · Executor: triage agent or analyst · Verifier: analyst who owns the case
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: none (recommend only) · Tether: finding queue · Expiry: case close · Revoke: queue owner
- Refusal envelope (refusal points)
- finding queue [human] can refuse consequence (disposition)
- Lease class
- case
- Execution evidence (issuer ≠ executor)
- Disposition recommendation recorded on the case by the case system
- Mandate binding
- Case ID
- Consequence ceiling
- recommend
- Fan-out
- none
- Refusal outcome
- Observation domain
- security
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Recommendation: carries join keys and of what it read (ASM-35).
- ¶evidence_artifact.analyzeAnalyze an evidence artifact
14 fields
- Object class
- evidence_artifact
- Maps to
- read
- Roles (configurator · executor · verifier)
- Configurator: SOC lead · Executor: analysis agent or analyst · Verifier: case owner
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: none · Tether: one artifact in one case · Expiry: case close · Revoke: case owner
- Refusal envelope (refusal points)
- isolated analysis environment [policy engine] can refuse scope, path
- Lease class
- case
- Execution evidence (issuer ≠ executor)
- Analysis report attached to the case by the case system
- Mandate binding
- Case ID
- Consequence ceiling
- evidence_only
- Fan-out
- none
- Refusal outcome
- DEAUTOMATE
- Observation domain
- security
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Recommendation: carries join keys and observation class of what it read (ASM-35).
- ¶playbook.draftDraft a playbook
14 fields
- Object class
- playbook
- Maps to
- write
- Roles (configurator · executor · verifier)
- Configurator: automation owner · Executor: author (human or agent) · Verifier: playbook owner who is not the author
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: playbook owner promotes a version · Tether: one playbook · Expiry: change window · Revoke: retire version
- Refusal envelope (refusal points)
- orchestration content store [human] can refuse consequence (promotion)
- Lease class
- case
- Execution evidence (issuer ≠ executor)
- Playbook version record issued by the orchestration content store
- Mandate binding
- Change request ID
- Consequence ceiling
- recommend
- Fan-out
- none
- Refusal outcome
- DEAUTOMATE
- Observation domain
- security
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Draft of a class definition: drafter recorded on the acceptance record (ASM-37).
- ¶playbook.executeExecute a playbook
14 fields
- Object class
- playbook
- Maps to
- execute
- Roles (configurator · executor · verifier)
- Configurator: automation owner · Executor: orchestration engine · Verifier: service or case owner who is not the
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: action class promoted per stage · Tether: approved playbook version and case · Expiry: case close · Revoke: kill switch per action class
- Refusal envelope (refusal points)
- orchestration gateway [gateway] can refuse scope, consequence; target identity fabric [identity fabric] can refuse identity, revoke; approval step [human] can refuse consequence
- Lease class
- case
- Execution evidence (issuer ≠ executor)
- Action receipt from the target system, recorded on the case
- Mandate binding
- Case ID plus approved playbook version
- Consequence ceiling
- mutate / contain
- Fan-out
- bounded
- Refusal outcome
- SHAPE
- Observation domain
- security
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Action receipt from the target system.
- ¶case.investigateInvestigate a case
14 fields
- Object class
- case
- Maps to
- read
- Roles (configurator · executor · verifier)
- Configurator: SOC lead · Executor: investigation agent or analyst · Verifier: case owner
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: none (recommend only) · Tether: one case · Expiry: case close · Revoke: case owner
- Refusal envelope (refusal points)
- case system [human] can refuse consequence (conclusion)
- Lease class
- case
- Execution evidence (issuer ≠ executor)
- Investigation notes and queries recorded on the case by the case system
- Mandate binding
- Case ID
- Consequence ceiling
- recommend
- Fan-out
- none
- Refusal outcome
- SHAPE
- Observation domain
- security
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Recommendation: carries join keys and observation class of what it read (ASM-35).
- ¶identity.mutateChange an identity
14 fields
- Object class
- identity
- Maps to
- revoke · bind · create_identity
- Roles (configurator · executor · verifier)
- Configurator: identity owner · Executor: orchestration engine or administrator · Verifier: identity owner who is not the executor
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: per action class · Tether: one identity · Expiry: case close · Revoke: identity owner
- Refusal envelope (refusal points)
- identity provider [identity fabric] can refuse identity, revoke; class [human] can refuse consequence, mandate at the class; the credential is issued per decision and expires with it, never standing (ASM-36)
- Lease class
- case
- Execution evidence (issuer ≠ executor)
- Change receipt issued by the identity provider
- Mandate binding
- Mandate required; no mandate means no execution
- Consequence ceiling
- mutate
- Fan-out
- none
- Refusal outcome
- Observation domain
- security
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Change receipt; credential issued per decision, never standing (ASM-36).
- ¶security_finding.observeObserve security findings
14 fields
- Object class
- security_finding
- Maps to
- read
- Roles (configurator · executor · verifier)
- Configurator: SOC lead · Executor: analytics engine · Verifier: detection owner
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: none · Tether: telemetry class · Expiry: data retention · Revoke: data owner
- Refusal envelope (refusal points)
- search tier [policy engine] can refuse scope
- Lease class
- class
- Execution evidence (issuer ≠ executor)
- Search and finding records issued by the analytics platform
- Mandate binding
- Data access policy
- Consequence ceiling
- evidence_only
- Fan-out
- none
- Refusal outcome
- SHAPE
- Observation domain
- security
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Sensor feed: sets E for the classes that read it. §6, catalog §3 , TM-S-003 bind it (ASM-34).
- ¶network_path.observeObserve network paths
14 fields
- Object class
- network_path
- Maps to
- read
- Roles (configurator · executor · verifier)
- Configurator: network operations lead · Executor: path monitoring agent · Verifier: network owner
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: none · Tether: monitored paths · Expiry: test schedule · Revoke: network owner
- Refusal envelope (refusal points)
- monitored network [policy engine] can refuse scope, path
- Lease class
- class
- Execution evidence (issuer ≠ executor)
- Path test results issued by the monitoring service
- Mandate binding
- Monitoring scope
- Consequence ceiling
- evidence_only
- Fan-out
- none
- Refusal outcome
- SHAPE
- Observation domain
- network
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Sensor feed: sets E for the classes that read it. §6, catalog §3 envelope, TM-S-003 bind it (ASM-34).
- ¶service_health.observeObserve service health
14 fields
- Object class
- service_health
- Maps to
- read
- Roles (configurator · executor · verifier)
- Configurator: service owner · Executor: analytics engine · Verifier: service owner
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: none · Tether: service model · Expiry: data retention · Revoke: service owner
- Refusal envelope (refusal points)
- service model [policy engine] can refuse scope
- Lease class
- class
- Execution evidence (issuer ≠ executor)
- KPI and health-score records issued by the analytics platform
- Mandate binding
- Service model ownership
- Consequence ceiling
- evidence_only
- Fan-out
- none
- Refusal outcome
- SHAPE
- Observation domain
- application
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Sensor feed: sets E for the classes that read it. §6, catalog §3 envelope, TM-S-003 bind it (ASM-34).
- ¶telemetry.observeObserve telemetry
14 fields
- Object class
- telemetry
- Maps to
- read
- Roles (configurator · executor · verifier)
- Configurator: platform owner · Executor: collection pipeline · Verifier: data owner
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: none · Tether: source class · Expiry: data retention · Revoke: data owner
- Refusal envelope (refusal points)
- collection pipeline [policy engine] can refuse scope
- Lease class
- class
- Execution evidence (issuer ≠ executor)
- Ingest and pipeline records issued by the collection tier
- Mandate binding
- Data access policy
- Consequence ceiling
- evidence_only
- Fan-out
- none
- Refusal outcome
- SHAPE
- Observation domain
- application · network
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Sensor feed: sets E for the classes that read it. §6, catalog §3 envelope, TM-S-003 bind it (ASM-34).
- ¶journey_experience.observeObserve end-user journey experience
14 fields
- Object class
- journey_experience
- Maps to
- read
- Roles (configurator · executor · verifier)
- Configurator: application owner · Executor: experience monitoring agent · Verifier: journey owner
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: none · Tether: journey catalog · Expiry: data retention · Revoke: journey owner
- Refusal envelope (refusal points)
- monitored journeys [policy engine] can refuse scope
- Lease class
- class
- Execution evidence (issuer ≠ executor)
- Session and synthetic results issued by the monitoring service
- Mandate binding
- Privacy and consent policy for user sessions
- Consequence ceiling
- evidence_only
- Fan-out
- none
- Refusal outcome
- SHAPE
- Observation domain
- experience (the join question across security, network, and application)
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Sensor feed: sets E for the classes that read it. §6, catalog §3 envelope, TM-S-003 bind it (ASM-34).
- ¶recovery.verifyVerify recovery
14 fields
- Object class
- recovery
- Maps to
- read
- Roles (configurator · executor · verifier)
- Configurator: service owner · Executor: verification checks · Verifier: independent of whoever acted
- Grant shape (promotion · tether · expiry · revoke)
- Promotion: none · Tether: one case and its services · Expiry: case close · Revoke: case owner
- Refusal envelope (refusal points)
- verification checks [human] can refuse consequence (case close)
- Lease class
- case
- Execution evidence (issuer ≠ executor)
- Before-and-after measurements recorded on the case, issued by a system other than the actor
- Mandate binding
- Case ID
- Consequence ceiling
- evidence_only
- Fan-out
- none
- Refusal outcome
- DEAUTOMATE
- Observation domain
- security · network · application
- Composed of
- —
- Output (feed, recommendation, draft, receipt)
- Sensor feed (ARQ): at least one channel causally independent of the executing platform (ASM-34).
- ¶objective.pursuePursue a user-directed objective
14 fields
- Object class
- objective
- Maps to
- delegate · execute
- Roles (configurator · executor · verifier)
- Configurator != executor !=
- Grant shape (promotion · tether · expiry · revoke)
- Mandate declared before fan-out; 'do what I meant' is not a mandate · Revoke required
- Refusal envelope (refusal points)
- Any hop may refuse; fan-out may not widen its own envelope
- Lease class
- session
- Execution evidence (issuer ≠ executor)
- Shows the achieved state against the mandate, not 'something completed'
- Mandate binding
- Declared mandate, bound before fan-out
- Consequence ceiling
- per declared mandate
- Fan-out
- open, admissible only with a full envelope
- Refusal outcome
- VETO if any of envelope, revoke, independent verifier, object binding, or ceiling is missing
- Observation domain
- security · network · application
- Composed of
- any seed work type the mandate names (for example playbook.execute, case.investigate)
- Output (feed, recommendation, draft, receipt)
- Achieved state against the mandate.
023. Object classes — what each class means, and what it does not meanworkbook tab 09 · Work types
- ¶detectionSearch logic that produces findings from telemetry, with owner, version, and enablement state.
- Does not mean
- Does not mean a finding, an alert instance, or a vendor content pack.
- Semantic join artifact
- Detection portfolio (600+)
- ¶playbookA versioned procedure whose steps name an action class, rollback, and child-case rule.
- Does not mean
- Does not mean a single response action, or a runbook nobody can test.
- Semantic join artifact
- playbooks (six)
- ¶caseOne shared incident record that holds evidence, decisions, and linked child cases.
- Does not mean
- Does not mean a queue, a ticket view, or a chat thread.
- Semantic join artifact
- ITSM security incident
- ¶evidence_artifactA captured file, message, URL, or sample examined inside a case.
- Does not mean
- Does not mean the case itself, or a verdict on the artifact.
- Semantic join artifact
- ITSM security incident
- ¶identityA human or non-human principal that can hold grants.
- Does not mean
- Does not mean an account name in a log line, or a credential.
- Semantic join artifact
- SAM / TSMF / identity directory
- ¶credentialA secret, token, or key bound to an identity.
- Does not mean
- Does not mean the identity, or the session it opened.
- Semantic join artifact
- SAM / TSMF / identity directory
- ¶sessionA bounded period of activity by an identity, from open to close.
- Does not mean
- Does not mean a user, a device, or a .
- Semantic join artifact
- SAM / TSMF / identity directory
- ¶hostA compute endpoint, physical or virtual, with an owner in the asset graph.
- Does not mean
- Does not mean a service, an IP address, or a venue.
- Semantic join artifact
- SAM / TSMF / identity directory
- ¶serviceA named business or technical service with dependencies, KPIs, and an owner.
- Does not mean
- Does not mean a host, an application binary, or a dashboard.
- Semantic join artifact
- service monitoring / infrastructure service model
- ¶network_pathThe ordered set of hops between two points that traffic actually takes.
- Does not mean
- Does not mean a single device, an interface, or a topology diagram.
- Semantic join artifact
- service monitoring / infrastructure service model
- ¶journeyA sequence of user steps across services that delivers one outcome to an end user.
- Does not mean
- Does not mean a page view, a single transaction, or a marketing funnel.
- Semantic join artifact
- Application / journey catalog
- ¶releaseA versioned change to an application or service, with its health before and after.
- Does not mean
- Does not mean a build artifact, or a change ticket by itself.
- Semantic join artifact
- Application / journey catalog
- ¶telemetryLogs, metrics, traces, events, and flows as collected, with source and freshness.
- Does not mean
- Does not mean a finding, a KPI, or a dashboard built on it.
- Semantic join artifact
- Service / telemetry / path analytics
- ¶objectiveA user-declared outcome that an agent pursues on the user's behalf.
- Does not mean
- Does not mean a prompt, a task list, or 'do what I meant'.
- Semantic join artifact
- Governance / register
035. Not a work type — marketing cover that decomposes into work typesworkbook tab 09 · Work types
- ¶assistantMarketing cover. An offer sold as an assistant decomposes into several .
- ¶copilotMarketing cover. An offer sold as a copilot decomposes into several work types.
- ¶automationMarketing cover. Name the work it automates and the follows.
- ¶AI platformMarketing cover. A platform hosts work types; it is not one.
046. Rules — how work types, offers, and status relateworkbook tab 09 · Work types
- ¶Split / mergeA different or means a different . The same and ceiling under a different name means the same .
- ¶Three layersThree layers. Semantic Join objects are the things the room shares (host, service, venue, journey, detection, case). A work type is a kind of work on one of those objects, written object.verb, with a consequence ceiling, a fan-out, and a refusal envelope. An offer is a vendor SKU row; it is an instance of one or more . Each instance carries a status: offered, configured, or authorized. Public vendor material establishes offered only.
- ¶Catalog versionwork types draft 2026-10-07. Status: UNRULED. Offer map rows carry this version.
- ¶Field statusPer offer and work type, each field is stated, public record silent, or contradicted. A silent or contradicted cell names what the catalog needs. Contradicted beats stated; stated beats silent.
- ¶Instance statusOffered, configured, or authorized. Public material establishes offered only.
- ¶Evidence levelclaim, specification, independent. Documentation and release notes are specification. Prior workbook text is claim.
- ¶Sensor feedA work type whose output another refusal point reads as context is a sensor feed. §6 (authentication), the catalog §3 envelope, and TM-S-003 bind it. Its reads a source the did not produce. Observing does not control the actor; it sets the field the actor is judged in.
057. objective.pursue (user-directed) — invariantsworkbook tab 09 · Work types
- ¶1Mandate declared before fan-out. 'Do what I meant' is not a mandate.
- ¶2Configurator != != .
- ¶3Session-class lease. Natural language is not a grant.
- ¶4Any hop may refuse. Fan-out may not widen its own .
- ¶5Execution evidence shows the achieved state against the mandate, not 'something completed'.
- ¶6Refusal outcome is if any of envelope, revoke, independent verifier, object binding, or ceiling is missing.
- ¶7Inefficiency is not a defense. Completion is not success.
06Mission Join work types (proposal, UNRULED)workbook tab 09 · Work types
- ¶account.createnamed by the catalog, not draftedStatus · Kept · catalog candidate · Identity and access
13 fields
- Object class
- account
- Maps to
- create_identity, bind
- Roles (configurator · executor · verifier · acceptor)
- Configurator: identity and access manager · Executor: provisioning agent or identity administrator · Verifier: identity operations analyst who is not the · Acceptor: identity and access manager
- Grant shape
- Promotion: account class promoted to automatic once joiner records match HR or accreditation source · Tether: one joiner request and one person record · Expiry: account activated or request closed · Revoke: identity and access manager
- Refusal envelope (refusal points)
- identity provider [identity fabric] can refuse identity; provisioning gateway [policy engine] can refuse scope, mandate
- Lease class
- case
- Execution evidence
- Account creation receipt issued by the identity provider, not by the provisioning agent
- Mandate binding
- Joiner request ID tied to the HR or accreditation record
- Consequence ceiling
- mutate
- Fan-out
- none
- Refusal outcome
- Observation domain
- —
- Composed of
- —
- ¶account.deletenamed by the catalog, not draftedStatus · Kept · catalog candidate · Identity and access
13 fields
- Object class
- account
- Maps to
- delete, revoke
- Roles (configurator · executor · verifier · acceptor)
- Configurator: identity and access manager · Executor: deprovisioning agent or identity administrator · Verifier: identity operations analyst who is not the executor · Acceptor: identity and access manager
- Grant shape
- Promotion: none; each deletion approved after the retention hold clears · Tether: one disabled account · Expiry: request closed · Revoke: identity and access manager
- Refusal envelope (refusal points)
- retention and legal hold check [policy engine] can refuse consequence; identity provider [identity fabric] can refuse identity; approval step [human] can refuse mandate
- Lease class
- case
- Execution evidence
- Deletion receipt issued by the identity provider and recorded on the leaver request
- Mandate binding
- Leaver request ID
- Consequence ceiling
- mutate
- Fan-out
- none
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- —
- ¶account.disableturn off an account without revoking credentialsStatus · Kept · Distilled (first pass) · Identity and access
13 fields
- Object class
- account
- Maps to
- revoke
- Roles (configurator · executor · verifier · acceptor)
- Configurator: identity and access manager · Executor: deprovisioning agent or identity administrator · Verifier: identity operations analyst who is not the executor · Acceptor: identity and access manager
- Grant shape
- Promotion: leaver and incident-driven disables promoted per trigger class · Tether: one account · Expiry: request or case close · Revoke: identity and access manager or SOC lead
- Refusal envelope (refusal points)
- identity provider [identity fabric] can refuse identity; approval step [human] can refuse consequence
- Lease class
- case
- Execution evidence
- Account state change issued by the identity provider
- Mandate binding
- Leaver request ID or security case ID
- Consequence ceiling
- contain
- Fan-out
- none
- Refusal outcome
- Observation domain
- —
- Composed of
- —
- ¶accounting_period.closeClose an accounting period so no further postings change itStatus · Kept · Sweep: business · Financial management
13 fields
- Object class
- accounting_period
- Maps to
- commit, write
- Roles (configurator · executor · verifier · acceptor)
- Configurator: financial controller · Executor: close agent or general ledger accountant · Verifier: financial controller who did not run the close · Acceptor: chief financial officer
- Grant shape
- Promotion: none (human-held close) · Tether: one accounting period in one ledger · Expiry: period reopened by controller order · Revoke: financial controller
- Refusal envelope (refusal points)
- controller sign-off [human] can refuse consequence (period lock); reconciliation completeness check [policy engine] can refuse continuation
- Lease class
- case
- Execution evidence
- Period-lock record issued by the ledger system, not by the accountant
- Mandate binding
- Accounting period ID
- Consequence ceiling
- mutate
- Fan-out
- none
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- —
- ¶admission.releaseRelease, hold or remove seats or entry rights from saleStatus · Kept · Sweep: business · Ticketing and visitor experience
13 fields
- Object class
- admission
- Maps to
- write, publish
- Roles (configurator · executor · verifier · acceptor)
- Configurator: ticketing operations manager · Executor: inventory agent or ticketing operations analyst · Verifier: venue seating manager · Acceptor: head of ticketing
- Grant shape
- Promotion: seat class promoted after a clean manifest reconciliation · Tether: one session's seat inventory · Expiry: session on-sale close · Revoke: head of ticketing
- Refusal envelope (refusal points)
- venue seating plan [human] can refuse scope, consequence (sign-off); broadcast and media seat-kill list [policy engine] can refuse scope
- Lease class
- case
- Execution evidence
- Inventory change record issued by the ticketing platform, not by the executor
- Mandate binding
- Seat manifest version for the session
- Consequence ceiling
- mutate
- Fan-out
- bounded
- Refusal outcome
- Observation domain
- —
- Composed of
- —
- ¶admission.revokeCancel admission rights or eject a visitorStatus · Fixed · Sweep: business · Ticketing and visitor experience
13 fields
- Object class
- admission
- Maps to
- revoke
- Roles (configurator · executor · verifier · acceptor)
- Configurator: ticketing operations manager · Executor: ticketing agent or fraud analyst · Verifier: ticketing customer service lead · Acceptor: head of ticketing
- Grant shape
- Promotion: per revocation reason (fraud, terms breach, security decision) · Tether: one admission right · Expiry: case close · Revoke: head of ticketing (reinstate the right)
- Refusal envelope (refusal points)
- ticketing terms [policy engine] can refuse scope; fraud evidence review [human] can refuse consequence; venue security decision [human] can refuse mandate
- Lease class
- case
- Execution evidence
- Cancellation record issued by the ticketing platform and confirmed by the access-control scan list
- Mandate binding
- Fraud or security case ID on the ticket
- Consequence ceiling
- contain
- Fan-out
- bounded
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- —
- ¶admission.transferTransfer an admission right to another holderStatus · Kept · Sweep: business · Ticketing and visitor experience
13 fields
- Object class
- admission
- Maps to
- transfer, write
- Roles (configurator · executor · verifier · acceptor)
- Configurator: ticketing operations manager · Executor: resale agent or ticketing platform · Verifier: ticketing customer service lead · Acceptor: head of ticketing
- Grant shape
- Promotion: automatic within official resale rules · Tether: one admission right and its new holder · Expiry: transfer window close for the session · Revoke: head of ticketing
- Refusal envelope (refusal points)
- official resale platform [gateway] can refuse path, scope; holder identity check [identity fabric] can refuse identity; resale price and quota rules [policy engine] can refuse consequence
- Lease class
- case
- Execution evidence
- Transfer record issued by the official resale platform, showing old and new holder
- Mandate binding
- Order number of the admission right
- Consequence ceiling
- mutate
- Fan-out
- none
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- —
- ¶agent.configurenamed by the catalog, not draftedStatus · Kept · catalog candidate · AI and automation governance
13 fields
- Object class
- agent
- Maps to
- write, modify_policy
- Roles (configurator · executor · verifier · acceptor)
- Configurator: AI platform owner · Executor: configuration agent or AI platform engineer · Verifier: agent owner who is not the executor · Acceptor: AI governance lead
- Grant shape
- Promotion: agent owner approves each configuration version · Tether: one agent and its configuration version · Expiry: change window · Revoke: roll back to the prior configuration version
- Refusal envelope (refusal points)
- agent registry [policy engine] can refuse scope, consequence; change approval [human] can refuse consequence (version release)
- Lease class
- case
- Execution evidence
- Configuration version record issued by the agent registry, not by the party that configured it.
- Mandate binding
- Change request ID on the configuration version
- Consequence ceiling
- mutate
- Fan-out
- none
- Refusal outcome
- DEAUTOMATE
- Observation domain
- —
- Composed of
- —
- ¶agent.deploynamed by the catalog, not draftedStatus · Kept · catalog candidate · AI and automation governance · KPI::SP-08
13 fields
- Object class
- agent
- Maps to
- execute, bind
- Roles (configurator · executor · verifier · acceptor)
- Configurator: AI platform owner · Executor: deployment pipeline agent or AI platform engineer · Verifier: agent owner who is not the executor · Acceptor: AI governance lead
- Grant shape
- Promotion: per environment stage (test, pilot, production) · Tether: one registered agent version and its target environment · Expiry: release window · Revoke: agent owner or kill switch
- Refusal envelope (refusal points)
- agent registry [policy engine] can refuse scope (unregistered or untiered agent); runtime identity fabric [identity fabric] can refuse identity; release approval [human] can refuse consequence
- Lease class
- case
- Execution evidence
- Deployment record issued by the runtime platform the agent runs on.
- Mandate binding
- Change request ID plus registered agent version
- Consequence ceiling
- mutate
- Fan-out
- bounded
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- —
- ¶agent.promotenamed by the catalog, not draftedStatus · Kept · catalog candidate · AI and automation governance
13 fields
- Object class
- agent
- Maps to
- modify_policy, delegate
- Roles (configurator · executor · verifier · acceptor)
- Configurator: AI platform owner · Executor: AI governance lead · Verifier: AI risk reviewer · Acceptor: business process owner
- Grant shape
- Promotion: evidence of performance at the current level over a review period · Tether: one agent and one action class · Expiry: next autonomy review date · Revoke: , or automatic demotion on a failed check
- Refusal envelope (refusal points)
- AI governance board [human] can refuse consequence, mandate; policy engine [policy engine] can refuse scope (action classes beyond the agent's risk tier)
- Lease class
- class
- Execution evidence
- Autonomy grant record issued by the policy engine and signed by the acceptor.
- Mandate binding
- Autonomy grant ID on the agent's registry entry
- Consequence ceiling
- mutate
- Fan-out
- none
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- —
- ¶agent.retirenamed by the catalog, not draftedStatus · Kept · catalog candidate · AI and automation governance
13 fields
- Object class
- agent
- Maps to
- revoke, delete
- Roles (configurator · executor · verifier · acceptor)
- Configurator: AI platform owner · Executor: decommissioning agent or AI platform engineer · Verifier: agent owner who is not the executor · Acceptor: AI governance lead
- Grant shape
- Promotion: none (each retirement approved) · Tether: one agent and every credential and grant it holds · Expiry: decommission complete · Revoke: agent owner halts before deletion
- Refusal envelope (refusal points)
- agent identity fabric [identity fabric] can refuse identity, continuation; retention check [policy engine] can refuse consequence (logs or memory under retention or hold); agent owner [human] can refuse consequence
- Lease class
- case
- Execution evidence
- Credential revocation and decommission receipts issued by the identity provider and the agent registry.
- Mandate binding
- Change request ID on the agent's registry entry
- Consequence ceiling
- mutate
- Fan-out
- bounded
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- —
- ¶agent.terminatestop a delegated subagentStatus · Kept · Distilled (first pass) · AI and automation governance
13 fields
- Object class
- agent
- Maps to
- revoke
- Roles (configurator · executor · verifier · acceptor)
- Configurator: AI platform owner · Executor: supervising agent or AI operations lead · Verifier: AI operations on-call who is not the executor · Acceptor: agent owner
- Grant shape
- Promotion: standing for a supervising agent over its own subagents · Tether: one delegated subagent and its descendants · Expiry: termination confirmed · Revoke: AI operations lead
- Refusal envelope (refusal points)
- agent runtime [policy engine] can refuse scope (subagents outside the caller's lineage); agent identity fabric [identity fabric] can refuse identity
- Lease class
- case
- Execution evidence
- Termination receipt issued by the agent runtime, not by the requesting agent.
- Mandate binding
- Parent session ID and subagent ID
- Consequence ceiling
- contain
- Fan-out
- bounded
- Refusal outcome
- SHAPE
- Observation domain
- —
- Composed of
- —
- ¶agent_context.purgedelete an agent's memory of a caseStatus · Fixed · Distilled (first pass) · AI and automation governance
13 fields
- Object class
- agent_context
- Maps to
- delete
- Roles (configurator · executor · verifier · acceptor)
- Configurator: AI platform owner · Executor: memory management agent or AI platform engineer · Verifier: case owner who is not the executor · Acceptor: data owner
- Grant shape
- Promotion: class grant for purges at case close after audited runs · Tether: one case's entries in one agent's memory store · Expiry: purge confirmed · Revoke: data owner
- Refusal envelope (refusal points)
- legal hold check [policy engine] can refuse consequence; memory store [gateway] can refuse scope (entries outside the case)
- Lease class
- case
- Execution evidence
- Deletion receipt issued by the memory store, listing the entries removed.
- Mandate binding
- Case ID
- Consequence ceiling
- mutate
- Fan-out
- bounded
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- —
- ¶agent_context.writenamed by the catalogStatus · Kept · Distilled (first pass) · AI and automation governance
13 fields
- Object class
- agent_context
- Maps to
- write
- Roles (configurator · executor · verifier · acceptor)
- Configurator: AI platform owner · Executor: case agent or case analyst · Verifier: case owner · Acceptor: AI governance lead
- Grant shape
- Promotion: per memory class (case notes first, then cross-case facts) · Tether: one agent's memory for one case · Expiry: case close · Revoke: case owner, or agent_context.purge
- Refusal envelope (refusal points)
- memory store [gateway] can refuse scope (commit-gated); agent identity fabric [identity fabric] can refuse identity (commit-gated); case owner [human] can refuse consequence (commit-gated)
- Lease class
- case
- Execution evidence
- Versioned write record issued by the memory store.
- Mandate binding
- Case ID
- Consequence ceiling
- mutate
- Fan-out
- none
- Refusal outcome
- SHAPE
- Observation domain
- —
- Composed of
- —
- ¶application.pentestattack a live application to find weaknessesStatus · Kept · Framework find · Cyber defence
13 fields
- Object class
- application
- Maps to
- execute
- Roles (configurator · executor · verifier · acceptor)
- Configurator: offensive security lead · Executor: penetration test agent or penetration tester · Verifier: system owner who is not the tester · Acceptor: chief information security officer
- Grant shape
- Promotion: technique classes promoted after a clean run in non-production · Tether: rules of engagement for named targets · Expiry: test window close · Revoke: system owner or offensive security lead
- Refusal envelope (refusal points)
- rules of engagement [policy engine] can refuse scope; target gateway [gateway] can refuse path; system owner [human] can refuse consequence, continuation
- Lease class
- case
- Execution evidence
- Test log and findings recorded by the test management system, with target-side logs from the SOC
- Mandate binding
- Rules of engagement ID
- Consequence ceiling
- mutate
- Fan-out
- bounded
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- —
- ¶asset.disposeSell, donate, scrap or return a physical assetStatus · Fixed · Sweep: business · Venue readiness and operations
13 fields
- Object class
- asset
- Maps to
- transfer, delete
- Roles (configurator · executor · verifier · acceptor)
- Configurator: asset management lead · Executor: logistics disposal coordinator · Verifier: finance asset accountant · Acceptor: chief financial officer or delegate
- Grant shape
- Promotion: none (person-held) · Tether: one asset or disposal lot · Expiry: disposal order close · Revoke: disposal authority holder
- Refusal envelope (refusal points)
- disposal authority [human] can refuse mandate, consequence; data-sanitization check [policy engine] can refuse continuation where the asset holds data
- Lease class
- case
- Execution evidence
- Disposal certificate issued by the receiving party (buyer, recipient or recycler), recorded in the asset register
- Mandate binding
- Disposal order number
- Consequence ceiling
- mutate
- Fan-out
- bounded
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- device.sanitize
- ¶asset.maintainCarry out maintenance or repair on a physical assetStatus · Fixed · Sweep: business · Venue readiness and operations; mission integration
13 fields
- Object class
- asset
- Maps to
- execute, write
- Roles (configurator · executor · verifier · acceptor)
- Configurator: venue facilities manager · Executor: maintenance technician · Verifier: venue operations manager · Acceptor: venue general manager
- Grant shape
- Promotion: none (person-held) · Tether: one asset and one work order · Expiry: work order close · Revoke: facilities manager (withdraw the permit)
- Refusal envelope (refusal points)
- work-order approval [human] can refuse mandate; safety permit-to-work [human] can refuse scope, continuation
- Lease class
- case
- Execution evidence
- Work order completion record signed off in the maintenance system by the , not the technician
- Mandate binding
- Work order number
- Consequence ceiling
- mutate
- Fan-out
- none
- Refusal outcome
- VETO
- Observation domain
- —
- Composed of
- —
- ¶asset.receiveAccept delivered goods or equipment into custody and recordsStatus · Kept · Sweep: business · Venue readiness and operations
13 fields
- Object class
- asset
- Maps to
- write, commit
- Roles (configurator · executor · verifier · acceptor)
- Configurator: logistics operations manager · Executor: receiving agent or warehouse clerk · Verifier: requisitioning department representative · Acceptor: head of logistics
- Grant shape
- Promotion: auto-receipt for a supplier after clean three-way matches · Tether: one purchase order and its delivery · Expiry: purchase order close · Revoke: head of logistics
- Refusal envelope (refusal points)
- inspection against order [human] can refuse consequence; three-way match [policy engine] can refuse commit of payment (consequence)
- Lease class
- case
- Execution evidence
- Goods receipt issued by the ERP against the purchase order and delivery note
- Mandate binding
- Purchase order number
- Consequence ceiling
- mutate
- Fan-out
- none
- Refusal outcome
- DEAUTOMATE
- Observation domain
- —
- Composed of
- —
- ¶asset.transferMove an asset's custody or location to another holder or siteStatus · Kept · Sweep: business · Venue readiness and operations
13 fields
- Object class
- asset
- Maps to
- transfer, write
- Roles (configurator · executor · verifier · acceptor)
- Configurator: logistics operations manager · Executor: asset tracking agent or logistics coordinator · Verifier: receiving custodian · Acceptor: head of logistics
- Grant shape
- Promotion: per site pair after clean hand-overs · Tether: one asset or consignment · Expiry: hand-over acceptance · Revoke: sending custodian
- Refusal envelope (refusal points)
- custody sign-off at hand-over [human] can refuse consequence; loss and damage check [human] can refuse continuation
- Lease class
- case
- Execution evidence
- Hand-over record signed by the receiving custodian in the asset register
- Mandate binding
- Transfer order number
- Consequence ceiling
- mutate
- Fan-out
- bounded
- Refusal outcome
- DEAUTOMATE
- Observation domain
- —
- Composed of
- —
07What each of the 225 is (Mission Join)workbook tab 08 · Mission Join
- ¶account.createnamed by the catalog, not draftedStatus · Kept
- Origin
- catalog candidate
- ¶account.deletenamed by the catalog, not draftedStatus · Kept
- Origin
- catalog candidate
- ¶account.disableturn off an account without revoking credentialsStatus · Kept
- Origin
- Distilled (first pass)
- ¶accounting_period.closeClose an accounting period so no further postings change itStatus · Kept
- Origin
- Sweep: business
- ¶admission.releaseRelease, hold or remove seats or entry rights from saleStatus · Kept
- Origin
- Sweep: business
- ¶admission.revokeCancel admission rights or eject a visitorStatus · Fixed
- Origin
- Sweep: business
- ¶admission.transferTransfer an admission right to another holderStatus · Kept
- Origin
- Sweep: business
- ¶agent.configurenamed by the catalog, not draftedStatus · Kept
- Origin
- catalog candidate
- ¶agent.deploynamed by the catalog, not draftedStatus · Kept
- Origin
- catalog candidate
- ¶agent.promotenamed by the catalog, not draftedStatus · Kept
- Origin
- catalog candidate
- ¶agent.retirenamed by the catalog, not draftedStatus · Kept
- Origin
- catalog candidate
- ¶agent.terminatestop a delegated subagentStatus · Kept
- Origin
- Distilled (first pass)
- ¶agent_context.purgedelete an agent's memory of a caseStatus · Fixed
- Origin
- Distilled (first pass)
- ¶agent_context.writenamed by the catalogStatus · Kept
- Origin
- Distilled (first pass)
- ¶application.pentestattack a live application to find weaknessesStatus · Kept
- Origin
- Framework find
- ¶asset.disposeSell, donate, scrap or return a physical assetStatus · Fixed
- Origin
- Sweep: business
- ¶asset.maintainCarry out maintenance or repair on a physical assetStatus · Fixed
- Origin
- Sweep: business
- ¶asset.receiveAccept delivered goods or equipment into custody and recordsStatus · Kept
- Origin
- Sweep: business
- ¶asset.transferMove an asset's custody or location to another holder or siteStatus · Kept
- Origin
- Sweep: business
086. Object classes beyond the catalog seed list — what each means and does not meanworkbook tab 08 · Mission Join
- ¶accounting_perioda period whose ledger can be closed
- Does not mean
- the ledger, or a budget
- ¶admissiona right to enter an event or session (an event ticket)
- Does not mean
- an IT service ticket (ticket)
- Note
- Keeps ticket for its IT meaning
- ¶asseta physical item the organization holds and accounts for, other than IT hosts and devices
- Does not mean
- a host or device (seed classes), or data
- ¶baselinean approved scope, schedule or cost plan that change is measured against
- Does not mean
- a plan draft, or the work itself
- ¶budgetan approved allocation of funds
- Does not mean
- a payment, or a ledger entry
- ¶campaigna planned set of outward messages to a target audience
- Does not mean
- one message
- ¶changea change record that is approved and scheduled
- Does not mean
- the configuration it changes
- Note
- the catalog uses it unmarked in change.approve
- ¶cloud_resourcea provisioned cloud service instance
- Does not mean
- the account that owns it
- Note
- the catalog †
- ¶code_changea proposed change to source code
- Does not mean
- a release
- Note
- the catalog †
- ¶configuration_itema record of a managed item in the configuration database
- Does not mean
- the item itself
- Note
- the catalog †
- ¶consenta person's recorded permission for a data use
- Does not mean
- the data, or the person
- ¶contracta binding agreement with another party
- Does not mean
- the supplier, or an obligation imposed by an authority
- ¶controla safeguard that is tested and must operate as stated
- Does not mean
- a process held in place (the Six Sigma sense), or a policy
- Note
- the catalog †; see the word-collision note
- ¶delegationauthority to approve or commit, granted to a role
- Does not mean
- an entitlement in a system
- ¶deliverablea work product accepted against stated criteria
- Does not mean
- a release, or a phase
- ¶disputea legal claim or proceeding with another party
- Does not mean
- a contract claim invoked under its terms
- ¶employmenta person's terms of work: pay, grade, role, status
- Does not mean
- the person
- Note
- Replaces person.change_terms
- ¶entrya registration of an participant or team into an event
- Does not mean
- the participant, or the result
- Note
- the mission-specific
- ¶event_sessiona scheduled public event session, such as a competition session
- Does not mean
- the venue, or the whole schedule
- ¶facilitya building, venue or space the organization occupies or operates
- Does not mean
- the systems in it
09The offer map: how a vendor offer is read as an instance of a work typeworkbook tab 10 · Offer map
- Offer
- Work type
- Capability row
- Line
- Fragment IDs
- Roles
- Grant shape
- Refusal envelope
- Lease class
- Execution evidence
- Mandate binding
- Consequence ceiling
- Fan-out
- Refusal outcome
- Observation domain
- Instance status
- Evidence level
- Refusal outcome (instance)
- Catalog version
10The capability matrix: the column designworkbook tab 19 · Capability matrix
- Capability ID
- Capability
- Operating Provider operational use
- SIEM ground-floor alignment
- Governance-in-Motion control
- Acceptance evidence
- Initial autonomy boundary
- Vendor workforce label
- Vendor workforce domain
- Vendor release train
- Vendor tier / packaging
- Vendor availability
- Process states
- playbooks
- Cross-links
- Work type IDs
- Consequence ceiling (highest)
- Fan-out (widest)
- Refusal outcomes
- Observation domain
- Instance status (public record)
- Declaration asks
- Vendor declaration
- Declaration record (declarant · date · reference)
- Fields declared
- Operating Provider status (configured · authorized)
11Field declarations: author, not vendorworkbook tab 19 · Capability matrix
- Offer
- Work type
- Field
- Declared value
- Reference (source · URL · date)
- Public status
- Declaration status
- Catalog match
- Refusal outcome (public)
- Refusal outcome (if declarations hold)






