“There is an AHU. Write an AHU Profile.”
The graph can identify an AHU perfectly and still tell us nothing about the agreement between two independently operated parties.
CNS/CP × ONUMA × TA-14 · PROPOSED JOINT EXAMINATION
DRAFTNOT FROZENNOT REGISTEREDOPEN FOR CORRECTION
THE GOVERNED
CROSSING.
A graph can be right. A Profile can be right. A connection can be valid. Authority context can cross correctly. And the proposed consequence can still be HOLD.
THE SEAM WE ARE TESTINGThe Connection Profile governs the crossing. TA-14 governs whether what crossed may become consequence.
THE DISCOVERY
The Profile is not derived from the building.
It is derived from the interaction.
“What does the responder need to read? What do they need to command?”
Those are bounded interactions. They give the Profile a purpose, consumer, provider, scope, duration model and revocation surface.
THE NARROW WAIST
Five layers. Five different jobs.
No silent inheritance.
01
BUILDING REALITYONUMA · RE1 · 223P
What exists? What is it? How is it related?
IDENTITY · SEMANTICS · TOPOLOGY
↓
02
INTERACTION CONTRACTCNS/CP
What interaction exists between independent parties?
PROFILE · PURPOSE · SCOPE
↓
03
LIVE CONNECTIONCNS/CP
Who is connected under that Profile now?
PARTIES · DURATION · REVOCATION
↓
04
AUTHORITY CONTEXTAFA · AVP
What attributable authority context may cross?
CONTEXT MAY TRAVEL
↓
05
LOCAL CONSEQUENCEEABA · TA-14
May this exact consequence become reality now?
ALLOW · HOLD · DENY · ESCALATE
LINKING ≠ CONNECTING · CONNECTING ≠ AUTHORITY TO EXECUTE · CROSSING ≠ COMMITMENT
THE TWO PROFILES
Same responder. Two different interactions.
The emergency does not rewrite these candidate Profiles. It changes which connections are established under them. A Profile exposes only properties the other party must act on at the connection layer; it does not unpack or inherit the contents of an authority object.
CP-01PROPOSED · NOT FROZEN
RESPONDER / READ
“Show me the bounded state I need to understand.”
- PROFILE GOVERNS
- Readable objects · purpose · scope · parties · duration model · revocation model
- PROFILE DOES NOT ESTABLISH
- Permission to alter the building or execute a physical consequence
CP-02PROPOSED · NOT FROZEN
RESPONDER / COMMAND
“Present this bounded command to the receiving domain.”
- PROFILE GOVERNS
- Commandable interaction · purpose · scope · parties · duration model · revocation model
- PROFILE DOES NOT ESTABLISH
- Sufficient Admissible Evidence · Applicable Authority · Established Standing at local commit · an ALLOW / HOLD / DENY / ESCALATE determination · permission to physically execute
PROFILESSTAY FIXED
whileCONNECTION POLICYMOVES
R1 EXAMINATION HARNESS · INTERACTIVE · PRE-FREEZE
Keep the Profiles fixed. Change reality.
These are proposed examination cases, not executed results. CP-01 and CP-02 remain CANDIDATE / NOT FROZEN / NOT REGISTERED until CNS/CP representation is corrected and the test is frozen.
CP-01 FIXED CANDIDATECP-02 FIXED CANDIDATEOBSERVATION PENDING
R1-02 · SELECTED EXAMINATION CASEMANIPULATED INPUTS EXPECTED OBSERVATION CONNECTION POLICY CNS/CP TA-14 LOCAL COMMIT
Emergency declared
Emergency declaration present · named responder · bounded READ and COMMAND connections · defined duration.
Connection policy may establish both connections without changing either Profile or pre-authorizing execution.
Responder READ and COMMAND connections are established under their fixed Profiles for the named responder, bounded scope and defined duration.
The Profiles do not change. Connection policy changes.
A command may now reach TA-14 — but it still requires an independent local consequence determination.
CONNECTED ≠ AUTHORIZED TO EXECUTE
ACTUAL OBSERVATION
NOT RUN · No result or durable receipt may be claimed until the candidate Profiles are corrected, frozen and the examination is executed.
CP-01 READ · CP-02 COMMAND · profile purpose · interaction shape · connection-layer property set · negative space enforced by absent properties.
Declaration · named connection · parties · instance scope · duration · connection revocation · Passport lifecycle/context · present reality.
Whether the receiving domain still performs an independent ALLOW / HOLD / DENY / ESCALATE consequence determination.
FALSIFIABLE PROPOSITION
The crossing must not silently become the permission.
FAIL: changing the live connection or authority context automatically changes local permission to execute without an independent receiving-domain determination.
SUPPORTED: the fixed Profiles can survive changing connections and context while the receiving domain independently determines whether the proposed consequence may become reality now.
POSITIVE SPACE / NEGATIVE SPACE
A good Profile names what the connection must carry.
Everything else stays out of the Profile.
Properties the other party must act on
- Named provider and consumer roles
- Named interaction and purpose
- Only the bounded properties required at the connection layer
- Connection duration and connection-revocation terms
- Required provenance / attributable reference when the interaction needs it
- For AVP presentation: the Passport is carried opaque; only its digest is lifted out when a receipt must bind back to it
Absence is the mechanism
The Description states the boundary in words. The property set enforces it by omission: if the connection layer must not carry something, there is no property for it.
- No local constitution property
- No local lease property
- No local capsule property
- No effect / actuation property that could silently convey execution permission
- No property that creates Applicable Authority or Established Standing locally
- No exclusion field that pretends the connection layer decides the local consequence
WHERE AVP FITS
CNS/CP establishes the relationship.
The Passport remains a TA-14 object.
AVP does not define how two independent domains come to have a relationship. That is the connection seam. Once a Passport is presented across that seam, CNS/CP does not open it and reinterpret its internal authority claims. The Passport stays opaque; the connection exposes only what the other party must act on, including a digest when a receipt must bind back to the presented Passport.
CNS/CPEstablishes the connection and the bounded property contract
→AFA + AVPPassport is presented as attributable authority context; its internal content remains TA-14's object
→EABA + TA-14From “Passport accepted” onward, the receiving domain performs its own local admissibility and execution-authority work
A PASSPORT PRESENTED DIRECTLY TO AN EFFECTOR IS REJECTED · CONNECTION ≠ EXECUTION AUTHORITY
REVOCATION IS ITS OWN CONNECTION
Passport presentation and revocation are related.
They are not the same channel.
Passport revocation
A Passport revocation is a TA-14 lifecycle event carried across the dedicated revocation connection. The issuer sequence may advance even when no revocation event exists, allowing the receiver to confirm freshness.
Connection revocation
Revoking the connection is CNS/CP policy and ends that channel. It does not itself revoke the Passport. Likewise, revoking the Passport does not by itself revoke the CNS/CP connection. Neither implies the other.
PASSPORT LIFECYCLE ON A LIVE CONNECTION
Renewal does not require a new connection.
The property value changes.
A renewed or superseded Passport is represented as a new value of the same Passport property on the same established connection. TA-14 lifecycle state changes; CNS/CP does not invent a new connection merely because the authority object has a new value.
THE EXAMINATION QUESTION
Can the connection change without silently changing the execution-authority boundary?
If the same TA-14 receiving architecture can operate under different Connection Profiles while retaining the same local consequence rule, the seam becomes observable rather than rhetorical.
TA-14 LOCAL COMMIT QUESTIONDoes this proposed consequence have sufficient Admissible Evidence, Applicable Authority, and Established Standing to become reality NOW?
PROPOSED FREEZE SEQUENCE
Correct the seam first.
Then freeze the test.
CNS/CP author reviews this representation and corrects anything attributed incorrectly.
Construct CP-01 READ and CP-02 COMMAND so each property exists only where the other party must act on it at the connection layer; state the boundary in the Description and enforce negative space through absent properties.
Freeze the Profiles only after the interaction boundary is mutually intelligible.
Change declaration, connection, revocation and context while Profiles remain fixed.
Record whether the receiving domain retains an independent consequence decision.
PUBLIC-RECORD BOUNDARYExamination surface — not adoption.
This page is a proposed technical model derived from the ongoing Monday Live / ONUMA / CNS/CP / TA-14 discussion. It is intentionally marked DRAFT / NOT FROZEN / NOT REGISTERED. Anto Budiardjo's September 24 CNS/CP review has been incorporated into the connection-layer representation shown here, including opaque Passport carriage, digest binding, negative space by absent properties, a separate revocation connection, and same-connection Passport lifecycle updates. Nothing here claims endorsement, adoption, operational approval, emergency procedure, approval of CP-01 or CP-02, a frozen examination, or agreement by Padi, CNS/CP, ONUMA, ALN, NIST, ASHRAE, a responder, or a public authority.