01
Name the object
ResourceType fixes the schema, relations, actions, and exact definition revision.
Awaken Objects · governed business objects
Early preview Early access by requestLet people and Agents act from the same business facts.
Turn identities, relationships, and allowed changes from existing systems into typed, versioned object records with explicit provenance.
For data, business-system, operations, and internal-application teams. Choose one important business object and identify the system that already owns it.
Product model preview · example content, with type, provenance, and revision semantics from the current implementation
Product model preview · example content
Business object
Example: an order controlled by an external system and observed through a Connector.
ResourceType
Exact revision
Identity authority
External system
Object view
Exact snapshot
RecordFactState
Order · example Connector observation Observed
Customer relation Resolved by external identity Resolved
approve Action Requires authority and revision Available
Latest change Source and time retained Recorded
Objects keeps a typed, sourced object record. The external system still owns its business fact; an Action returns the governed result.
Start with one object
Make one business concept understandable before connecting every system.
Take an Order as an example. Define its identity and fields, connect it to a Customer, record which system supplied each observation, and expose only the actions that system allows. The example is configurable product behavior, not a built-in Order package.
02
Observe the source
A Connector normalizes external identity, properties, relations, source, and observation time.
03
Offer allowed change
An Action names what may change and requires authorization, an expected revision, and an idempotency boundary.
What Objects owns
An object record is governed context, not a copy of Agent memory.
Objects keeps the typed record that applications and Agents may use. It distinguishes platform-owned state from externally controlled state and never turns a Connector observation into exclusive authority.
Type and identity
ResourceType defines the contract. Resource preserves identity, exact type revision, and lifecycle.
Snapshot and relation
A consumable ResourceSnapshot freezes one revision; Relation connects exact objects without guessing the latest value.
Observation and provenance
Connector observations retain provider or fallback identity, mechanism, time, and optional provider ordering evidence.
Action and receipt
Read-only, idempotent, and mutating Actions follow one authorization and revision-fenced execution path.
One governed change
A proposal becomes usable only after the owning boundary returns a result.
01 Observe
A Connector brings back normalized identity, properties, relations, and provenance.
02 Project
Objects exposes an exact typed snapshot rather than an unversioned latest value.
03 Propose
A person, application, or Agent submits one named Action with expected revision and idempotency key.
04 Authorize and call
Objects checks authority and revision before the configured provider boundary is invoked.
05 Record the result
The receipt and next observation make the accepted external result available to every authorized consumer.
Boundary
Connect business truth. Do not manufacture a second system of record.
Not a data warehouse
Objects does not replace analytical storage or ingest every source before one useful object can exist.
Not Agent memory
Context assembled for a run is a consumer of the object record, never its lifecycle authority.
Not universal write access
An Agent may propose only declared Actions; current authorization and revision are checked on every call.
Start with one object, one source, and one governed action.
Read the current model, then request early access if you have one object and source-system boundary to explore.