This page is a trust asset, not an embarrassment.
Every line below states a status, names the source it comes from, and says what it means in plain language. Nothing here is softened for effect.
Verify is not certified. An independent re-audit of these exact bytes has not been completed.
V Verified against source bytes Where this comes from
- Source file
00_START_HERE/02-CURRENT-TRUTH.md- Section
- Claims prohibidos
- File digest
- 289ae963be25b5a563e29a88c29b0811564a1b96c287208755ad07013a2a6d62
- Verbatim quote
`CERTIFIED=YES`: NO hasta reauditoría independiente de AC7.
10_LIMITS/01-NO-CONSTA-REGISTER.md records Certification as NO_CONSTA and independent re-audit as PENDING.
Verify is a reference implementation. Production readiness is conditional on a deployment preflight passing on the target host, which has not been done.
V Verified against source bytes Where this comes from
- Source file
00_START_HERE/02-CURRENT-TRUTH.md- Section
- Claims prohibidos
- File digest
- 289ae963be25b5a563e29a88c29b0811564a1b96c287208755ad07013a2a6d62
- Verbatim quote
`PRODUCTION_READY=YES`: condicionado a `DEPLOYMENT-PREFLIGHT=PASS` sobre el host objetivo.
No deployment preflight was run by this build, and no deployment was performed.
Resistance to a same-user rollback of single-use state is not provided. It needs a durable external anchor this candidate does not implement.
V Verified against source bytes Where this comes from
- Source file
10_LIMITS/00-KNOWN-LIMITS.md- Section
- Límites conocidos
- File digest
- 269a0d9458686d58057e48a273ac17d40348901fa6d11c7fcc9a90970b44486b
- Verbatim quote
Rollback-resistant one-use requiere ancla externa/monotónica
Recorded in the NO_CONSTA register as NOT_PROVIDED, and in CURRENT-TRUTH as RES-FINAL-001.
There is no trusted external clock. Expiry is judged against the host's own clock.
V Verified against source bytes Where this comes from
- Source file
10_LIMITS/00-KNOWN-LIMITS.md- Section
- Límites conocidos
- File digest
- 269a0d9458686d58057e48a273ac17d40348901fa6d11c7fcc9a90970b44486b
- Verbatim quote
Trusted external time no existe; expiración usa reloj del sistema.
Listed as CODE_PATH_ABSENT in the NO_CONSTA register.
Key custody uses a local key in the reference material. There is no production KMS or HSM integration.
V Verified against source bytes Where this comes from
- Source file
10_LIMITS/00-KNOWN-LIMITS.md- Section
- Límites conocidos
- File digest
- 269a0d9458686d58057e48a273ac17d40348901fa6d11c7fcc9a90970b44486b
- Verbatim quote
External Authority Reference usa clave Ed25519 local; no KMS/HSM productivo.
KMS/HSM custody is CODE_PATH_ABSENT in the NO_CONSTA register.
Of the effects the reference gate can perform, only file creation is enabled. Deletion is switched off and fails closed.
V Verified against source bytes Where this comes from
- Source file
10_LIMITS/00-KNOWN-LIMITS.md- Section
- Límites conocidos
- File digest
- 269a0d9458686d58057e48a273ac17d40348901fa6d11c7fcc9a90970b44486b
- Verbatim quote
Sólo CREATE_FILE está habilitado; DELETE_FILE está fail-closed por decisión del Owner.
Owner decision recorded in source. This website does not expose the gate at all.
The reference gate reduces syscall surface and can apply host-conditional filesystem restriction. That is surface reduction, not a complete sandbox.
V Verified against source bytes Where this comes from
- Source file
10_LIMITS/00-KNOWN-LIMITS.md- Section
- Límites conocidos
- File digest
- 269a0d9458686d58057e48a273ac17d40348901fa6d11c7fcc9a90970b44486b
- Verbatim quote
Seccomp es denylist default-ALLOW y se documenta como reducción de superficie, no sandbox completo.
Landlock is conditional on the host and is not credited when unavailable.
There is no exhaustive formal verification, and no transparency log or durable external anchor.
V Verified against source bytes Where this comes from
- Source file
10_LIMITS/00-KNOWN-LIMITS.md- Section
- Límites conocidos
- File digest
- 269a0d9458686d58057e48a273ac17d40348901fa6d11c7fcc9a90970b44486b
- Verbatim quote
No formal verification exhaustiva.
Item 14 of the same list records the absence of a transparency log or durable external anchor.
Structural diversity in the evidence is not proof of physically independent producers, and Verify does not claim otherwise.
V Verified against source bytes Where this comes from
- Source file
10_LIMITS/00-KNOWN-LIMITS.md- Section
- AC6 · límites de assurance
- File digest
- 269a0d9458686d58057e48a273ac17d40348901fa6d11c7fcc9a90970b44486b
- Verbatim quote
la independencia física real sigue sin inferirse de `producer_id`
Recorded fixture INSUFFICIENT_INDEPENDENCE shows the structural check returning NO_CONSTA, not a claim of real independence.
Who holds and distributes the external root of trust in production is not established by this candidate.
NC No consta: recorded as unestablished Where this comes from
- Source file
10_LIMITS/01-NO-CONSTA-REGISTER.md- Section
- NO_CONSTA / CODE_PATH_ABSENT
- File digest
- e6b1aaf20601469e522378bd81c9b0037e41f98dac095147747dae337054a700
- Verbatim quote
| Custodia externa de Stage-0/pins | `NO_CONSTA` |
Published as NO_CONSTA. This is a documented absence, not a defect being hidden.
There is no hosted Verify API. The API on this site is a published contract, not a running service.
NC No consta: recorded as unestablished Where this comes from
- Source file
10_LIMITS/01-NO-CONSTA-REGISTER.md- Section
- NO_CONSTA / CODE_PATH_ABSENT
- File digest
- e6b1aaf20601469e522378bd81c9b0037e41f98dac095147747dae337054a700
- Verbatim quote
| Production deployment | `NO_CONSTA` |
No backend was built and no endpoint was deployed by this build. The OpenAPI document is labelled SPEC throughout.
The reference test suite runs green in this workspace. That accredits development, not independent certification.
V Verified against source bytes Where this comes from
- Source file
00_START_HERE/02-CURRENT-TRUTH.md- Section
- Evidencia
- File digest
- 289ae963be25b5a563e29a88c29b0811564a1b96c287208755ad07013a2a6d62
- Verbatim quote
Los tests builder-side acreditan desarrollo. La certificación independiente permanece separada.
108 of 108 tests were reproduced locally against the sealed snapshot. The result is recorded as a builder-side run, not an audit.
How a status gets recorded here
This build reproduced the AC7 reference test suite against the sealed snapshot: 108 of 108 tests passed. That accredits development in this workspace. It is not, and is not presented as, an independent audit.
How a limit gets recorded here.
How this works
- 01
The object is named, not described vaguely
Key custody, trusted time, rollback resistance — each limit is about one specific thing rather than a general disclaimer.
- 02
A source is cited, with its digest
Every line opens to show the exact file inside the sealed source it came from, that file’s digest, and a quote the build verified is present in it.
- 03
It is classified by how it is known
Verified against bytes, reported, inferred, or no consta — recorded as unestablished. A gap keeps its own label rather than borrowing a stronger one.
- 04
The build refuses to publish a drifted claim
If a quote no longer appears in its source file, generation fails and nothing ships. A limit cannot quietly stop being true.
Step by step
-
Pick any line below and open "Where this comes from".
You will see a file path, a digest, and a quote in the original language of the source.
That means the limit is not our opinion. It is what the source material itself records.
-
Look at the letter in the small box — V, R, I or NC.
You will see how that statement is known.
That means V was checked against the bytes. NC means nobody has established it, and we are saying so rather than guessing.
-
Compare this page with the maturity tags elsewhere on the site.
You will see the same vocabulary: IMPLEMENTED, DEMO, REFERENCE, SPEC, PLANNED, NO_CONSTA.
That means one honesty scale across the whole product, not a separate softer one for marketing.