Capabilities as bounded outcomes

1. Problem → outcome → stage

   Controlled model access

   1. 01

      Customer problem

      Model calls need routing authority, usage evidence, and a clear separation from semantic judgment.

   2. 02

      Intended outcome

      Each model invocation can be represented as a controlled responsibility transfer with bounded evidence.

   3. 03

      Responsible stages

      • Model access authority — Conexus
      • Governed run — Allagma

   Evidence boundary: Routing and call evidence do not establish semantic truth.

   Inspect the complete capability path

2. Problem → outcome → stage

   Dossier and offline verification

   1. 01

      Customer problem

      Reviewers need a durable record and a way to detect whether published files differ from their manifest.

   2. 02

      Intended outcome

      The decision loop ends at an inspectable dossier and an independent checksum-verification boundary.

   3. 03

      Responsible stages

      • Evidence system-of-record — ALL
      • Temporal evidence and reconstruction — Aisthesis

   Evidence boundary: Checksum matching does not prove a decision correct, complete, or legally compliant.

   Inspect the complete capability path

3. Problem → outcome → stage

   Governed execution

   1. 01

      Customer problem

      External runtimes can perform work without making their authority boundaries or consequential actions inspectable.

   2. 02

      Intended outcome

      A run can be explained as an ordered set of bounded operations, gates, and evidence-producing handoffs.

   3. 03

      Responsible stages

      • Governed run — Allagma
      • Promotion authority — ARG
      • Shared mechanics — Ontogony.Platform

   Evidence boundary: Execution does not silently acquire semantic or promotion authority.

   Inspect the complete capability path

4. Problem → outcome → stage

   Promotion and officialization

   1. 01

      Customer problem

      Produced results can appear official when the authority required to promote them is implicit or absent.

   2. 02

      Intended outcome

      Promotion becomes a distinct, fail-closed responsibility with an inspectable result.

   3. 03

      Responsible stages

      • Promotion authority — ARG
      • Semantic authority — Kanon
      • Evidence system-of-record — ALL

   Evidence boundary: A technical promotion gate is not a legal or regulatory determination.

   Inspect the complete capability path

5. Problem → outcome → stage

   Semantic and policy judgment

   1. 01

      Customer problem

      Model output alone cannot determine which facts, policies, or interpretations are authoritative.

   2. 02

      Intended outcome

      A decision record can distinguish advisory output from the authority that judged it.

   3. 03

      Responsible stages

      • Semantic authority — Kanon
      • Promotion authority — ARG

   Evidence boundary: Model output remains advisory unless a named authority promotes it.

   Inspect the complete capability path

6. Problem → outcome → stage

   Temporal reconstruction

   1. 01

      Customer problem

      Later review needs to establish what evidence was available when a consequential decision was made.

   2. 02

      Intended outcome

      A reviewer can follow declared source lineage and time-indexed context without assuming undocumented completeness.

   3. 03

      Responsible stages

      • Source intake and lineage — Metabole
      • Temporal evidence and reconstruction — Aisthesis
      • Evidence system-of-record — ALL

   Evidence boundary: Reconstruction is limited to the evidence actually present and linked.

   Inspect the complete capability path

See the responsibilities in the full loop