SwarmForge

01Authority boundary

A decision before the effect.

The public contract separates a candidate action, its authority decision and any later execution report.

  • Dispatch decisions retain policy and provenance snapshots.
  • Execution grants bind a decision to a capability, subject and validity window.
  • Unknown outcomes remain unknown instead of being recast as success or failure.
Generated editorial illustration for “A decision before the effect.”: The public contract separates a candidate action, its authority decision and any later execution report. It is not product proof.

02Identity and provenance

The requester survives the whole chain.

The contract carries verified identity and authority context across every safety-relevant command.

  • Tenant, principal, reason and correlation travel in the command envelope.
  • Authority is bound to verified credentials and context, never trusted from the request body alone.
  • Server-issued identifiers and timestamps remain authoritative.
Generated editorial illustration for “The requester survives the whole chain.”: The contract carries verified identity and authority context across every safety-relevant command. It is not product proof.

03Capability policy

Authority lives outside the prompt.

Versioned capabilities and policies define the effective regime independently of model instructions.

  • The contract records the regime, classification source, reason, actor and version.
  • An absent policy resolves to denial in the contract semantics.
  • Changes to authority or state transitions are treated as breaking changes.
Generated editorial illustration for “Authority lives outside the prompt.”: Versioned capabilities and policies define the effective regime independently of model instructions. It is not product proof.

04Approval and halt

Not on your own is a real decision.

Approval and halt are explicit state machines, not a generic yes-or-no button.

  • Approval can finish approved, rejected or expired; terminal states never reopen.
  • Dual approval keeps the request pending after the first distinct signer.
  • A halt can be engaged or lifted; lifting it never deletes its history.
Generated editorial illustration for “Not on your own is a real decision.”: Approval and halt are explicit state machines, not a generic yes-or-no button. It is not product proof.

05Execution and observation

A decision is not an observed effect.

The contract treats permission, external execution and observation as separate facts.

  • A grant is bound to the decision and capability; it does not prove an effect.
  • Execution reports move monotonically and preserve uncertain outcomes.
  • An observation carries source, authenticity and freshness, and never commands execution.
Generated editorial illustration for “A decision is not an observed effect.”: The contract treats permission, external execution and observation as separate facts. It is not product proof.

06Reference implementation

A trace contains the decision.

In SwarmForge Platform, the reference implementation correlates the requester, policy decision, human choice, execution and observed effect.

  • The trace records observable decisions, not the model’s internal reasoning.
  • Execution acknowledgement and observed effect remain distinct.
  • Later alteration is described as detectable, never impossible.
Generated editorial illustration for “A trace contains the decision.”: In SwarmForge Platform, the reference implementation correlates the requester, policy decision, human choice, execution and observed effect. It is not product proof.

07Paid technical evaluation

Evaluate the boundary on your workflow.

A paid technical evaluation will map the contract to your workflow before any claim of production authority.

  • Identify safety-relevant commands and their effective regimes.
  • Select fixtures for denial, approval, halt, stale context and uncertain execution.
  • Record proven compatibility and every remaining gap.
Discuss the governance boundary
Generated editorial illustration for “Evaluate the boundary on your workflow.”: A paid technical evaluation will map the contract to your workflow before any claim of production authority. It is not product proof.