coulomb/net-kingdom
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Intake NET-IN-0002: amend tenant-engine boundary contract
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Requested by tenant-engine TEN-WP-0011-T06 after the v0.7 Engine/PIP
declaration and shipped guardrails.

Assistant: grok
Assistant-Session: 01a04cea-e5e8-7081-a0fc-808ebbc35fa9
This commit is contained in:
tegwick 2026-08-29 13:02:58 +02:00
parent 66dc491dc0
commit 9a7f5c9337
1 changed files with 38 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

38
intakes/intakes.md
View file

@ -33,3 +33,41 @@ description: 'A conformance sweep on 2026-08-28 found this repository has no lay
created: '2026-08-28T21:01:51.894396Z'
updated: '2026-08-28T21:01:51.894396Z'
```
## NET-IN-0002 — Amend tenant-engine-boundary-contract_v0.1 for Engine/PIP, shipped guardrails, and PEP-shaped writes
```yaml
id: NET-IN-0002
kind: intake
title: 'Amend tenant-engine-boundary-contract_v0.1 for Engine/PIP, shipped guardrails, and PEP-shaped writes'
status: open
origin: cross-repo
origin_ref: TEN-WP-0011-T06
priority: medium
owner: net-kingdom
requested_by: tenant-engine
description: >
tenant-engine has declared Engine / PIP under security-layer-model v0.7
(TEN-DEC-2026-001) and shipped guardrail/quota policy (TEN-WP-0006).
canon/standards/tenant-engine-boundary-contract_v0.1.md still says
guardrail/quota policy is "reserved, not yet implemented" and that
tenant-engine is "not a policy enforcement point". Both sentences now
mislead: guardrails are owned and served as PIP ceilings
(tenant-engine/docs/tenant-guardrail-policy.md), and writes are
PEP-shaped even though this repo is not a PDP.
Requested amendments, without forking the contract into tenant-engine:
1. Mark guardrail/quota policy as owned and implemented; point at
tenant-engine/docs/tenant-guardrail-policy.md.
2. Restate the authorization contract: data source / PIP for decisions;
PEP-shaped for its own protected writes; never a second PDP.
3. Mention Engine / PIP and security-layer-model_v0.7 next to the
existing IAM Profile / ADR-0013 / ADR-0014 references.
Do not assign approval lifecycle to tenant-engine (TEN-DEC-2026-001
contested that placement).
created: '2026-08-29'
updated: '2026-08-29'
```