Connected buildings
Development of building connectivity and integration technologies begins decades before today's digital-twin vocabulary.
ANTO BUDIARDJO · PADI.IO · MONDAY LIVE! · INTEROPERABILITY
Making connectivity explicit.
For decades, Anto Budiardjo has worked on the problem underneath smart buildings: independently designed systems must be able to form understandable, reusable relationships. Today that work is visible in CNS/CP and Connection Profiles — an architecture for naming and governing the connection itself.
PUBLIC PROFILEOPEN FOR CORRECTIONNO ENDORSEMENT IMPLIED
THE WORK BEHIND THE CONNECTION
Interoperability is not just getting the data through.
When systems multiply, one-off integrations become expensive, brittle and hard to reason about. Anto's work has repeatedly pushed toward a different model: make the relationship between systems explicit enough that people and software can understand what is connecting, why, and under what declared conditions.
NAME — Identify the provider and consumer.
A LONG CONNECTIVITY ARC
This did not start with digital twins or AI agents.
Padi.io's public biography traces Anto's connected-building work to 1989. The vocabulary has changed over time, but the recurring problem has remained recognizable: how independently governed systems form useful relationships without dissolving their boundaries.
Systems meet
The problem starts as getting independently designed building systems to exchange useful information without bespoke integration everywhere.
Context matters
The work moves beyond raw data transport toward shared meaning, relationships, roles, and the context surrounding a connection.
CNS / CP
Connection Profiles make the relationship explicit: who provides, who consumes, what crosses, and under what declared contract.
“Every connection between systems is governed by a named, immutable contract.”
SUMMARY OF THE CONNECTION PROFILE MODEL DESCRIBED IN ANTO'S 2026 PUBLIC WRITING · SEE SOURCE RECORD BELOW
THE INTEROPERABILITY SEAM
The connection layer and the consequence layer are different jobs.
This is the point where Anto's CNS/CP work and TA-14 can be examined together without collapsing one architecture into the other.
What may connect?
Name the provider and consumer roles. Define the Connection Profile. Establish the declared properties and context that may cross. Form and observe the relationship.
→
What may this connection cause?
When a proposed real-world consequence approaches Commit, establish Admissible Evidence, Applicable Authority and Established Standing for that exact consequence NOW.
Connection ≠ execution authority. A governed crossing can carry context while the authority to make a consequential change still has to be established where that consequence becomes real.
INTERACTIVE BOUNDARY EXAM
Does a valid Connection Profile authorize the downstream consequence?
Test the seam. The connection can be valid while execution authority remains a separate determination.
WHY IT MATTERS
A named relationship can be inspected, challenged and reused.
The relationship stops being hidden glue.
The connection becomes something that can be named, described and reasoned about instead of disappearing inside custom integration code.
A pattern can travel.
A Connection Profile can describe a reusable relationship rather than forcing every project to rediscover the same integration contract.
Connectivity can remain distinct from consequence.
Knowing what crossed a connection does not by itself settle whether a later proposed action is authorized to become reality.
Important boundary: this is an independent TA-14 public profile and interoperability examination. It does not claim that Anto Budiardjo, Padi.io, CNS/CP, Monday Live!, the IBB Project or AutomatedBuildings.com adopts TA-14. CNS/CP remains independently stewarded; TA-14 remains independently governed. The seam is published so each side can be inspected and corrected without being merged by implication.
PUBLIC WORK SURFACE
Follow the architecture through the record.
Anto's public work spans building integration, cloud-native systems, context-driven interoperability, Connection Profiles, the IBB Project and the governance problem created when autonomous systems begin forming relationships at scale.
External links open the underlying public sources directly.
ANTO BUDIARDJO
The system does not become interoperable merely because two endpoints can exchange bytes.
The relationship itself needs structure. That is the through-line this showroom makes visible: from building integration to named, contextual, inspectable connectivity — and then to the next boundary, where connection meets consequence.