Gate: obligation-honored
The artifact fulfils the cross-cutting obligations it takes on.
| Property | Value |
|---|---|
| Checker | obligation-honored |
| Confronts | spec |
| Blocking by default — new project | yes |
| Blocking by default — existing project | no — informs |
How it measures
Section titled “How it measures”Confronts the CROSS-CUTTING OBLIGATIONS a project declares against reality: a node whose header carries the trigger attribute must appear in the files the obligation demands.
It is the class of defect no per-unit spec catches, because the duty lives OUTSIDE the unit. The case that motivated it is real: a new data model, carrying free-text annotations written by the user, was left out of the account-deletion script — personal data that would never be erased. The project had been bitten by this before, and the script itself carries a comment calling it a “silent LGPD violation”. It repeated, and none of the nine existing gates saw it, because every one of them looks INSIDE the unit.
The honest exception, and the third state. A node can waive itself with
obligation_waived: <name> — <reason> in the header, and the reason is MANDATORY: a waiver
without a justification is treated as absent. But waiving is not the only real case — the
most common one is that the duty is REAL and will be paid in another phase, when the handler
that consumes the table does not exist yet. Waiving would be a lie (the duty did not stop
existing), and leaving it red confuses ACKNOWLEDGED DEBT with forgetfulness, which is exactly
the distinction the pillar exists to preserve. obligation_pending: <name> — <when> asserts
three things — that the duty is known, that it still holds, and when it will be paid — and
the verdict is Pending, visible in the report and never Pass.
What separates it from its neighbours: doc-required charges a document the Structure
declared for a LAYER; this one charges the presence of a TOKEN in the files a named duty
points at, triggered by an attribute the node itself declares.
Declaring it
Section titled “Declaring it”gates: - name: obligation-honored on: [spec] check: obligation-honored