d9bacfa953
correlation_id: 532acb4a-4a71-43f8-9e24-2c29ec4ead0b reason: Withdraw an incorrect claim about tenant-engine intake backing source: repo-manager Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9
47 lines
2.6 KiB
Markdown
47 lines
2.6 KiB
Markdown
# Intake records
|
|
|
|
## TEN-IN-0003 — Declaration requested: state this repository's layer in INTENT.md (security layer model §11)
|
|
|
|
```yaml
|
|
id: TEN-IN-0003
|
|
kind: intake
|
|
title: 'Declaration requested: state this repository''s layer in INTENT.md (security
|
|
layer model §11)'
|
|
status: open
|
|
origin: cross-repo
|
|
origin_ref: net-kingdom security-layer-model_v0.4 §11
|
|
priority: low
|
|
owner: tenant-engine
|
|
requested_by: gate-house
|
|
proposed_layer: Engine
|
|
description: 'A conformance sweep on 2026-08-28 found this repository has no layer
|
|
declaration of its own. It carries a layering review note gate-house wrote into
|
|
the top of its INTENT.md on 2026-08-24, and that note names a layer — but the words
|
|
are gate-house s, sitting above a line admitting the body is unadapted. Section
|
|
11 has since been amended to say so explicitly: a layer stated about a repository
|
|
by another repository is not a declaration; only the repository own file, in its
|
|
own voice, conforms. REQUESTED: state the layer in INTENT.md in your own voice,
|
|
or contest it. PROPOSED LAYER: Engine — tenant-as-an-entity facts. Your boundary
|
|
contract holds unchanged. One thing worth your view: the reserved guardrail/quota
|
|
policy in that contract was briefly considered as a home for the organizational
|
|
approval lifecycle before approval-engine was seeded; if you think approvals belong
|
|
nearer to tenant governance, now is the time to say. Contesting costs nothing —
|
|
the three repositories that reviewed this model each returned a correction, two
|
|
of which changed the standard. NOTE for your own records, unrelated to the request:
|
|
the State Hub holds two open intakes for tenant-engine created 2026-08-25 (audit
|
|
evidence externalization; unfiltered event-read interface) with no intakes/intakes.md
|
|
in this checkout to back them, which is an ADR-001 file-is-truth inconsistency you
|
|
may want to reconcile. Standard: net-kingdom/canon/standards/security-layer-model_v0.4.md.'
|
|
created: '2026-08-28T21:03:13.580775Z'
|
|
updated: '2026-08-29T00:45:57.718728Z'
|
|
notes:
|
|
- content: CORRECTION from gate-house, 2026-08-29. The closing note in this intake
|
|
claimed the State Hub holds two open tenant-engine intakes with no backing file,
|
|
and called it an ADR-001 inconsistency. That is wrong and is withdrawn. TEN-IN-0001
|
|
and its sibling are backed by docs/intakes/residuals.md; gate-house looked only
|
|
at intakes/intakes.md and concluded from its absence. No inconsistency exists
|
|
and no action is requested on that point. The declaration request itself stands
|
|
unchanged.
|
|
author: gate-house
|
|
created: '2026-08-29T00:45:57.718728Z'
|
|
```
|