Area guide · 10 packages · Inspect a digest-bound permit
Governance, decisions and approvals
Resolve policy and review decisions into explicit evidence before consequential work is allowed to proceed.
What are you trying to do?
- What is a decision trace versus an execution permit?
- How does Connect bind a decision to the exact work?
- Where do human review and obligations enter the flow?
Why start with these packages
Suggested entry point
@lssm-tech/lib.contractspec-connectUse the existing packet authority and durable, signed decision boundaries.
Suggested entry point
@lssm-tech/lib.decision-runtimeUse deterministic predicates and decision-graph evaluation/conversion.
Suggested entry point
@lssm-tech/module.human-reviewInspect reusable human-review composition around governed work.
Suggested entry point
@lssm-tech/module.review-queueLocate review queue, assignment and decision-facing composition.
Practical steps
Step 01
Inspect a protected action
Follow its approval requirement, trusted actor/context and decision request. Locate the receipt store/signature ports and the point at which the executor re-reads or verifies the resulting permit.
Step 02
Trace a changed proposal
Compare the approved target with a changed input, stale plan or different scope. Use the maintained validation path to see which binding invalidates the old receipt and which review must be repeated.
Step 03
Check the operator experience
Review how pending, denied, expired, superseded and completed decisions appear in the queue. Link the operator back to the exact evidence and outcome rather than collapsing every non-success state into a generic failure.
Match the decision to the proposed work
Connect issues and verifies context, plan, mutation, diff and promotion decisions bound to digests. Production hosts use durable-required mode with injected receipt storage and signing. The README describes a permit as usable only after its receipt has been stored and exact read-back matches. Verification at the point of use checks freshness, scope and integrity. This gives a concrete integration rule: changing the target, plan or relevant context requires the corresponding decision binding to be reassessed.
Use decisions for branching, then enforce effects
DecisionRuntime evaluates shared predicates and immutable decision graphs without evaluating creator-authored code. It validates before execution, bounds complexity and traces, pins subgraphs by revision/digest, and produces replayable results. Form conversion lives in a dedicated adapter. Workflow conversion only admits exact outcome-operation revisions in the server-controlled allowlist; the workflow/product runtime still owns effect execution and authorization. Keep a graph evaluation trace available to explain why a branch was selected.
Make human review useful
HumanReview, ReviewQueue and the governance modules provide product composition around assignment, escalation and review outcomes. Present the exact proposed action, its scope, material changes and supporting evidence. A review record should identify the decision it produced and the work it applies to. Keep obligations visible: an allow decision can still require a host to fulfill conditions or persist evidence before an action is eligible. A button label or a previously granted role is not a replacement for that current decision.
Follow a practical path.
Inspect a protected action
Follow its approval requirement, trusted actor/context and decision request. Locate the receipt store/signature ports and the point at which the executor re-reads or verifies the resulting permit.
Trace a changed proposal
Compare the approved target with a changed input, stale plan or different scope. Use the maintained validation path to see which binding invalidates the old receipt and which review must be repeated.
Check the operator experience
Review how pending, denied, expired, superseded and completed decisions appear in the queue. Link the operator back to the exact evidence and outcome rather than collapsing every non-success state into a generic failure.
Packages in this area (10)
10 of 10 shown
- Open manual →
Provider-neutral assurance and compliance evidence correlation contracts for autonomous-company actions.
- Open manual →
Provider-neutral packet authority and durable decision receipts for ContractSpec Connect.
Use the existing packet authority and durable, signed decision boundaries.
- Open manual →
Deterministic, effect-free DecisionGraph and PredicateSpec runtime.
Use deterministic predicates and decision-graph evaluation/conversion.
- Open manual →
Provider-neutral economic evidence primitives for usage, cost, budget, replay, and projection refs.
- Open manual →
Feature flags and experiments module for ContractSpec applications
- Open manual →
Audit trail module for tracking and querying system events
- Open manual →
Reusable deterministic edition platform surfaces for resources, UI, workflows, storage, agents, and evidence.
- Open manual →
Governance and audit suite — policy editor, audit trail, and compliance surfaces for the Agent + Workflow pillar
- Open manual →
Generic tenant-scoped human review contracts, append-only decisions, and optional React surfaces.
Inspect reusable human-review composition around governed work.
- Open manual →
Review queue module: human-in-the-loop approval, escalation, audit-grade decision flows, and per-domain health probe.
Locate review queue, assignment and decision-facing composition.
What connects to this area
Identity and access
A decision must use trusted actor, scope and current entitlement.
Core contracts
The proposed action and its required approval must be named precisely.
Workflows and automation
The selected branch can reference a permitted workflow operation.
Delivery and infrastructure
Execution verifies the permit against the exact plan and current state.