Cognous Control Plane | Open Control Stack | Cognous
Open Control Stack/ Components/ Component 05 Group 03 · Declaration & Policy Control

Cognous Control Plane

An earlier yes is not a permanent credential.

A Python reference implementation for bounded agent authorization, effect-time revalidation and persistent runtime records. It connects declared actions, independently supplied authority, execution attempts and reconciliation.

View repository All components
The problem
Approvals go stale

A cached approval or a fluent explanation cannot show whether authority, evidence and approvals were still valid when the effect was attempted.

With Control Plane
Critical inputs rechecked just before each effect

The controller decides, revalidates authorization-critical inputs immediately before invoking the effect, and keeps decisions, attempts, observations and reconciliation as separate records.

What it provides
Bounded authorization

Manifest-bound proposals evaluated against explicit policy and an Authority Context supplied by a trusted resolver, outside the incoming request.

Effect-time checks

authorization-critical inputs revalidated immediately before each effect is attempted.

Lifecycle records

decisions, attempts, observations and reconciliation kept distinct, including unknown acknowledgements.

Persistent records

reload-and-append under a Linux sidecar lock, with atomic replacement and explicit persistence failures.

Developer tools

validation, policy examples, replay export, redaction and integrity helpers, each with documented assurance limits.

In the refund workflow

A synthetic refund is proposed under a bounded grant. The controller records its decision, rechecks current authority immediately before the effect and invokes the constrained adapter. After a timeout, reconciliation concerns the original effect: a fresh observed absence does not authorize a replacement, and accepted applied evidence can resolve delivery while preserving the interrupted history.

Try it

Trace one refund’s decision, revalidation and attempt records, then run the timeout case to see how reconciliation treats the original effect.

Open the repository →
What “effect time” means here

The recheck is per effect, on one host. Individual record transactions are protected, but decide, execute and reconcile are not one atomic transaction, and there is no distributed check-to-commit guarantee: authority can change between the recheck and the destination commit. Reconciliation records what happened; it does not undo it.

What it does not claim

Supports cooperating writers on documented local Linux filesystems with shared canonical-path assumptions. Production resolver authentication, distributed budgets, remote finality and exactly-once delivery are not established.