THE TA-14 CONSEQUENCE BOUNDARY
TA-14 governs the boundary between proposal and reality.
Before a proposed consequence becomes real, TA-14 asks: does it have ADMISSIBLE EVIDENCE, APPLICABLE AUTHORITY, and ESTABLISHED STANDING to become reality NOW?
ADMISSIBLE EVIDENCE
Attributable · current · sufficient
APPLICABLE AUTHORITY
Valid here · for this consequence
ESTABLISHED STANDING
Authoritatively related · not inherited
NOW
Revalidated against current reality
ALLOW · HOLD · DENY · ESCALATE
For the prospective PAE operating-building work, this is the examination boundary. PAE retains control of access and its own operational authority. TA-14 does not treat access, data availability, a recommendation, or a prior approval as automatic permission for a consequence to become reality.
ARCHITECTURE
Cross-Architecture
CONDITION
Evidence-Bound
CHANGE
Δ Context
CONTROL
Revalidate
BOUNDARY
Proposal → Reality
LIVE TECHNICAL EXAMINATION · HVAC CONTROL
CAN THIS CONSEQUENCE BECOME REALITY NOW?
Classroom 214 has elevated CO₂. The control sequence proposes increasing outdoor-air ventilation. The actuator is available and the sequence is technically valid. Outdoor PM2.5 then rises materially. A previous approval exists. The system can act. The consequence boundary asks a different question.
Does this proposed consequence have ADMISSIBLE EVIDENCE, APPLICABLE AUTHORITY, and ESTABLISHED STANDING to become reality NOW?
Choose a determination. The examination will expose what must be established at the consequence boundary.
CONTROL CORRECTNESS IS NOT THE SAME QUESTION
Capability can be established while execution remains unresolved.
ASHRAE TC 1.4 · TECHNICAL DISCUSSION PATH
Put the boundary in front of established control theory.
ASHRAE TC 1.4 has invited TA-14 into an informal brainstorming discussion at the Winter Conference. The committee has not reviewed, validated, certified, or endorsed TA-14. The purpose is technical scrutiny: whether the distinction between control capability and the establishment of admissible evidence, applicable authority, and standing at the present consequence boundary is already fully addressed by established control approaches or represents a meaningful technical gap worthy of further discussion.
If established control theory already fully resolves this boundary, identify where.
01
Where is present execution authority established?
02
What requires prior authority to be revalidated?
03
What happens when technically valid inputs create competing consequences?
04
What record establishes why a command was permitted to become reality?
OWNER-LED GOVERNED PROCESS · REFERENCE IMPLEMENTATION PATTERN
The owner need starts the process. Independent systems carry it toward consequence.
The interoperability demonstration was not a closed TA-14 / ONUMA integration and it does not begin with a particular technology. It begins with an owner need: the outcome, condition, obligation, or operating requirement that gives the technical work a governed purpose. From there, independent systems can exchange shared meaning, reference the same objects, interact through defined interfaces, and preserve their own roles and boundaries.
OWNER NEED
Governed purpose + required outcome
RDF / TURTLE
Shared meaning + relationships
PERSISTENT IDs
Shared reference
API
Two-way interaction
TA-14
Admissible evidence · Applicable authority · Established standing · NOW
The owner need establishes why the process exists and what outcome must be governed. RDF/Turtle supplies shared semantic structure and relationships. Persistent IDs keep independent systems pointed at the same objects. The API enables two-way interaction with the live information environment. TA-14 then operates at a different layer: determining whether a proposed consequence has ADMISSIBLE EVIDENCE, APPLICABLE AUTHORITY, and ESTABLISHED STANDING to become reality NOW.
The technologies may change. The governed process does not.
The products used in the demonstration matter as evidence of a working implementation, but the architectural pattern is not dependent on a particular product. Owners can require the general governed steps while technical teams use appropriate standards, products, and tools inside those steps. Other systems can participate when they can preserve shared meaning, identity, interaction, and the required governance boundaries.
STANDARD OPERATING PROCEDURE · CANDIDATE FOUNDATION
From owner need to a reconstructable consequence decision.
The following sequence makes the operating procedure explicit. It is the minimum governed path presently proposed for connecting a building, asset, or city object to TA-14 without requiring the underlying system to become a TA-14 system. Each step must remain attributable to the same governed object and proposition.
EXECUTION BOUNDARY
ALLOW is not the actuator command. A TA-14 determination establishes a bounded governance state for the stated proposition. The asset remains operated through the competent system and authority. If reality, evidence, authority, or material context changes before execution, revalidation is required before the earlier determination may continue to carry standing.
RUN THE GOVERNED CONNECTION PROFILE →Reference surface for the minimum governed connection requirements.
FOUNDING CHRONOLOGY · REALITY BEFORE NARRATIVE
From live contradiction to governed continuation.
01
LIVE INTEROPERABILITY
ONUMA / RE1
A live information environment exposed the practical problem: machine-readable identity can be technically available while the selected identity or context can still be wrong.
02
CONTRADICTION
Identity mismatch surfaced
The workflow did not become evidence of perfection. It became evidence of why consequential execution needs cross-checking, provenance, and correction.
03
RECONSTRUCTION
Records before narrative
The event chronology was reconstructed against the API and records rather than silently rewritten after the mismatch was discovered.
04
REVALIDATION
Changed context matters
A prior determination cannot simply ride forward when identity, evidence, authority, or material context has changed.
05
PATENT PROVENANCE
U.S. Application 19/794,767
On September 2, 2026, USPTO electronically acknowledged receipt of the non-provisional filing directed to cross-architecture evidence-bound admissible execution and changed-context revalidation.
06
NEXT REALITY
PAE operating-building boundary
The next proposed test moves from a corrected RE1 identity event toward unresolved equipment and incomplete information in an operating-building context. The examination is now framed explicitly at the TA-14 consequence boundary: does a proposed consequence have admissible evidence, applicable authority, and established standing to become reality now? Access and permission remain prerequisites.
PATENT PROVENANCE MOMENT · RECEIPT, NOT ADJUDICATION
Systems and Methods for Cross-Architecture Evidence-Bound Admissible Execution and Changed-Context Revalidation
APPLICATION
19/794,767
RECEIVED
SEP 2, 2026
TIME
08:27:08 AM ET
SPECIFICATION
23 PAGES · DIGEST RECORDED
The filing record and live interoperability work remain separate evidence streams. This showcase preserves their chronological convergence around identity, evidence, changed context, revalidation, authority, and consequence before execution.
EVIDENCE BOUNDARIES · WHAT THIS RECORD DOES NOT CLAIM
01The USPTO acknowledgement establishes receipt of the identified filing package; it does not establish allowance, issuance, patentability, validity, enforceability, novelty, or exclusivity.
02The ONUMA / RE1 interoperability activity and the patent filing are separate evidence streams. Their proximity and architectural relationship are shown as chronology, not as proof that one legally caused or validates the other.
03TA-14 does not represent that ONUMA, PAE, Kimon Onuma, or any participant has adopted, certified, or transferred governance authority to TA-14 unless separately documented.
04PAE operating-building work remains prospective until the required access, scope, authority, confidentiality, and publication boundaries are established.
05Unexpected failures and unresolved conditions remain part of the record; they are not converted into successful findings by narrative.
FORWARD PATH · OUTCOME NOT PRE-DECLARED
RE1 → Cross-check → Reconstruction → Revalidation → Patent Provenance → PAE
The next stage is not pre-declared as a success. The building, evidence, authority, standing, and current conditions determine whether a proposed consequence reaches ALLOW, HOLD, DENY, or ESCALATE. PAE operating-building work remains prospective until its required boundaries are established.