Time, states and versions
A shared contract for valid time, recorded time, revisions, states and schema versions without a universal domain lifecycle.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise contract
- Entry kind
- contract
- Domain
- EnterpriseXCT
- Industry
- Cross-industry
- Tags
- EM-XCT-04W0contractTemporalValidityRevisionLifecycleTransitionSchemaBinding
What it is Filled
A shared contract for valid time, recorded time, revisions, states and schema versions without a universal domain lifecycle.
Why it exists Filled
A shared contract for valid time, recorded time, revisions, states and schema versions without a universal domain lifecycle.
Distinguishing features Derived, awaiting review
- Schema version is not object revision
- Valid time is not recorded time
- Archiving does not destroy history
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: A single version=active stands in for both the schema version and the state.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Куратор мета-моделей Vercy
Master systems
- Реестр моделей
- sources.yaml
- vercy.lock
- политики
Links to other meta-models Filled
references
- WM-XCT-009 - conceptual-candidate
- WM-XCT-021 - conceptual-candidate
- WM-XCT-022 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- TemporalValidity
- Revision
- LifecycleTransition
- SchemaBinding
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- Current Vercy protocol/MMAS/whole-object and the published WM-XCT
- W3C PROV/SKOS/SHACL/ODRL where applicable
- Practice of source connectors, versioned schemas and policy enforcement
Open questions
- What was true, and what was known, as of a given date?
- How to correct retroactively?
- Which states belong to a specific domain?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-xct-04/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.