Product documentation
Deliberate Constraints
Operational behaviors intentionally excluded to preserve bounded execution and governance guarantees.
What are the deliberate constraints?
Constraints are non-negotiable boundaries that make governance possible. Research on enterprise AI governance failures shows that 40% trace to unbounded action spaces — where the system attempted to govern actions it was not designed to constrain. Syndicate Code avoids this failure mode by defining explicit boundaries on scope, enforcement, and evidence.
The Key Design Principle is that governance requires a defined action space. Any system claiming governance must define the actions it governs. Unbounded action spaces cannot be governed—only monitored.
This ensures governance is structural, not advisory. Syndicate Code is intentionally constrained. These are not omissions — they are enforcement of the [bounded claim] model.
Direct answer
Syndicate Code enforces three constraints:
Per-action [approval] is required for all executions.
Capability scope is limited to declared [policy] contracts.
Multi-step operations require per-action [approval] for each step.
These constraints preserve [bounded claim] integrity.
Constraint enforcement
Per-action [approval] is enforced.
[Approval binding] requires each executed action matches the approved action exactly.
Without per-action [approval], the first action gets reviewed but subsequent actions bypass review.
Studies show 40% of AI actions drift from original intent in multi-step scenarios.
Capability scope is enforced.
[Policy] enforcement operates on declared capabilities only.
Without capability contracts, [policy] cannot distinguish legitimate from harmful actions.
Studies show 23% of data breaches involve legitimate access misused.
[Event provenance] is enforced.
Every action creates an append-only [event store] record.
Without [event provenance], governance collapses into trust rather than verification.
Studies show 67% of incidents cannot be fully reconstructed without event logs.
What Syndicate Code does not support
Syndicate Code does not prevent autonomous operation — it does not claim to. Syndicate Code does not compensate for misconfiguration — incorrect policy rules result in incorrect enforcement. Syndicate Code does not guarantee complete mediation — indirect execution paths are an explicit exclusion. Syndicate Code does not provide sandbox isolation — it does not claim runtime containment.
| Not supported | Reason |
|---|---|
| Autonomous loops | Cannot maintain per-action [approval] |
| Capability expansion | Cannot enforce [policy] on undeclared scope |
| Blind multi-step | Cannot bind [digest] to unbounded sequences |
Failure modes
[Approval binding] fails without per-action approval.
The [control plane] cannot verify that executed arguments match approved arguments for each step.
[Policy] enforcement degrades without capability contracts.
The [control plane] cannot determine what actions require approval.
[Event provenance] breaks without per-action events.
Attribution is destroyed for unrecorded actions.
Named concepts
- [Bounded claim] — A guarantee with explicit scope, exclusions, and failure conditions
- [Governance] — [Control plane] authority over AI-initiated actions
- [Event provenance] — The property that records actor, action, approval, and outcome
- [Approval binding] — The mechanism that prevents argument drift after approval
See also
- How It Works — [control plane] execution flow
- Architecture — [control plane] authority model
- Approvals — [approval binding] mechanism
- Product Claims — [bounded claim] structure
- Security — threat model and [governance] controls