NIST WORKSHOP CONTEXT

This is a TA-14-created working presentation prepared for technical examination in the Stop the Cyber Attack workshop context. It is not a NIST publication and does not imply NIST endorsement, sponsorship, approval, adoption, validation or agreement with TA-14.

TA-14 WORKING CONTRIBUTION · NIST-FACING TECHNICAL SHOWROOM

FROM CONNECTION
TO CONSEQUENCE.

Eight visuals. One governed journey. Follow authority context across a federation, stop at the execution boundary, and examine what must be established before a proposed building consequence becomes reality.

WORKING PRESENTATION · OPEN FOR CORRECTION · NOT A NIST ENDORSEMENT · NO CLAIM OF NIST ADOPTION
THE TEACHING SEQUENCE
CP→AVP→AFA→EABA→AEA→REALITY

Core rule: Authority context can travel. Execution authority does not travel. It must be established locally before the proposed consequence can be admitted to reality.

WHAT CHANGES AT EACH LAYER?

Five mechanisms. Five different jobs.

CPCONNECTION

What may cross this specific doorway?

AVPCONTEXT

What authority context accompanies the actor or request?

AFAFEDERATION

How is that context governed across multiple entities?

EABALOCAL AUTHORITY

Has execution authority been established here, for this target?

AEACONSEQUENCE

May this proposed consequence become reality now?

CONNECTION SUCCESS≠EXECUTION PERMISSION

01 · THE FEDERATION

Independent domains. Shared context. No central execution authority.

Federation of independent domains participating in a governed information exchange
GUIDED WALKTHROUGH · LISTEN + READ

02 · THE CONNECTION

What may cross the connection?

Connection Profile governing what information may cross between domains
GUIDED WALKTHROUGH · LISTEN + READ

03 · THE EVIDENCE RETURN

The connection can return evidence about the same object.

Independent evidence returning across a governed connection and reconnecting to the same building object
GUIDED WALKTHROUGH · LISTEN + READ

04 · THE SAME OBJECT

Same object. Different proposed action. Different authority question.

AHU-1 shown with different proposed consequences requiring separate governance examination
GUIDED WALKTHROUGH · LISTEN + READ

05 · THE EVIDENCE GAP

Stop where the supplied evidence stops.

Evidence gap between EISO-1 and AHU-1 represented as an unresolved relationship
GUIDED WALKTHROUGH · LISTEN + READ

06 · THE CONSEQUENCE EXAMINATION

Examine the consequence, not the connection.

TA-14 consequence examination with evidence authority standing and four dispositions
GUIDED WALKTHROUGH · LISTEN + READ

07 · THE COMMIT BOUNDARY

ALLOW is not execution. Commit is the last governed boundary before release.

Commit boundary between governed determination and execution
GUIDED WALKTHROUGH · LISTEN + READ

08 · FROM CONNECTION TO CONSEQUENCE

The whole journey on one screen.

End-to-end teaching view from connection through governance commit execution and outcome
GUIDED WALKTHROUGH · LISTEN + READ
INTERACTIVE CONSEQUENCE CHECK

Change one condition. Watch the disposition change.

Toggle any condition below. The point is not to simulate a production authorization engine; it is to make the consequence boundary visible and inspectable.

ALLOW / HOLD THRESHOLD DEMONSTRATION

Can this proposed consequence cross the boundary now?

CURRENT TEACHING DISPOSITIONALLOW
Boundary condition satisfied for this simplified demonstration.Evidence, authority, and standing are all represented as established.
Teaching scope: this control demonstrates the ALLOW/HOLD threshold only. DENY and ESCALATE require additional policy conditions not represented in this simplified interaction.
THE CONSEQUENCE QUESTION

Does this proposed consequence have sufficient Admissible Evidence, Applicable Authority, and Established Standing to become reality NOW?

ALLOWHOLDDENYESCALATE
NIST CHALLENGE

Challenge the boundary, not the diagram.

Show where an existing mechanism already establishes the same present-tense evidence, local authority, exact target binding and standing immediately before Commit — and can withhold the consequence when one fails. Where that function already exists, record overlap or equivalence.

NO ADMISSIBLE EVIDENCE. NO ADMISSIBLE EXECUTION.
THE PROPOSITION TO EXAMINE

As systems become more capable, what must exist immediately before capability becomes physical consequence?

TA-14 is not arguing that intelligent buildings should become less intelligent, less connected or less automated. Connection matters. Information matters. Authority context matters. Intelligence matters. The proposition is narrower: none of those should silently become permission for a physical consequence.

01 · CHALLENGE IT

If this consequence boundary is drawn incorrectly, identify where and why.

02 · SHOW EQUIVALENCE

If an existing architecture already establishes the same present-tense evidence, local execution authority, exact target binding and standing immediately before Commit — and can withhold the consequence when one fails — show where that function occurs.

03 · EXAMINE THE GAP

If the boundary survives the challenge, examine what would be required to make the function operational, interoperable and testable.

THE MOMENT BEFORE CONSEQUENCE DESERVES ITS OWN EXAMINATION.Correction, equivalence or further examination are all useful outcomes.

Thank you for your time, for the opportunity to place this working proposition in front of NIST, and for giving TA-14 a moment to be examined.

OPEN PRESERVED WORKING EXAMINATION →