Semantic Engine
Constraint graph over concepts — contradictions surface as animated conflicts.
How you use it
Call semantic_enforce before declaring a feature finished or writing status/user-approved. Wire claims (done, shipped, milestone) to the graph — not prose habit.
Token savings
Kills premature “done” celebrations that trigger long user-correction threads. One failed enforce is cheaper than three rounds of “I thought it was finished.”
Consistency
Meaning is machine-checked: done ↔ user_approved, CAP states, and related concepts cannot contradict each other in commits or ledger status.
In action
Concepts + constraints from the semantic domain.
Interactive demo
Constraints
- Every commit declares exactly one Commit-Scope
- Confidence attestation precedes staging enforce
- Pointer rules must resolve for touched paths
- Semantic graph has no contradictory concept edges
Click a concept node to select it. Cyan = satisfied, fuchsia = contradiction. Simulated semantic graph only.
Simulated behavior only — does not execute proprietary AGS engine code.
Diagram
Example usage
// MCP: semantic_enforce
{}
// Constraint shape (conceptual)
concept: status-done
requires: user_approved
violation: User-approved: no Docs →- semantic_get
- semantic_validate
- semantic_enforce