# <Dimension name>

- Name: <human-readable Dimension name>
- Type: Vercy Dimension
- Purpose: <outcome this world supports>
- Owner: <owner identifier or role>
- Namespace: <stable namespace>
- Specification: ./dimension.yaml
- Storage binding: <local path, private repository, database or other binding>
- Interface binding: <filesystem, Git, MCP, database client or approved API>
- Installed models: ./vercy.lock
- Registries: ./registries/
- Policies: ./policies/
- Event log: ./registries/events.yaml
- Persistent memory: ./memory.yaml
- Federation: ./federation.yaml
- Context routing: ./context-routing.yaml
- Storage decision: ./bindings/storage.yaml
- Model agent protocol: https://ver.cy/model-agent-protocol.md
- Compatibility: ./compatibility.yaml
- Conflict policy: ./policies/conflict-resolution.yaml
- Runtime schemas: https://ver.cy/schemas/dimension/1.0/

This file MUST be created before any other Dimension data. Reuse known owner
facts and leave unknowns explicit; do not guess them. The Dimension remains in
the owner's environment and is private unless the owner explicitly declares a
different policy.

## Read order

1. Read `dimension.yaml`, `vercy.lock`, the applicable policy and the relevant
   model's `AGENTS.md`.
2. Resolve identity and mastership before copying or changing facts.
3. Use the nearest `AGENTS.md`; local rules may narrow but never silently widen
   this Dimension's authority or the public Vercy safety rules.
4. Read `memory.yaml`, `federation.yaml` and `context-routing.yaml`; load data
   from another Dimension only through an authorized projection.

## Delegated authority

Declare every relevant action under exactly one local level:

- `autonomous`: <safe reversible actions the agent performs and records>
- `propose`: <actions the agent may prepare but not apply>
- `confirm`: <actions requiring approval immediately before execution>
- `forbidden`: <actions the agent must not attempt>

Publication, access expansion, destructive change, external writes, secrets
and sensitive data MUST NOT default to `autonomous`.

## Operating loop

1. Understand the current task in the owner's language.
2. Check whether installed models can represent the required objects, states,
   events and actions.
3. If coverage is missing, search `https://ver.cy/models/runtime-index.json`.
   When policy grants `install-published-compatible`, install and connect the
   smallest fitting published closure without another question. Otherwise
   record a proposal.
4. Populate only from authorized sources. Record provenance, observation time,
   uncertainty and unanswered questions.
5. Validate identity, references, model rules, access and serialization before
   and after a write.
6. Record material changes as events and report exact paths, sources, results,
   remaining gaps and approvals needed.

Runtime objects, facts, relations and events are immutable JSON records. Use
the Vercy writer's separate `.vercy/write.lock` lease and an expected object
head; `vercy.lock` pins models and is not a mutex. Rebuild the replaceable
SQLite index for deterministic query. Resolve facts by both valid time and
recorded time; preserve equally authoritative disagreement as `contested`.
Apply only a declared migration after its dry-run.

The read plane may combine authorized Personal, Organization, project and
domain projections. The write plane assigns every fact to exactly one owning
Dimension and master system. Unknown ownership is quarantined as pending.

## Whole-object coverage

For every subject object, the installed model MUST explicitly classify these
facets as `required`, `optional`, `not-applicable` with a reason, or `delegated`
to another model: identity and class; direct properties; recognition and
observation; capabilities, behaviour and possible actions; context and
evidence. Do not invent physical properties for abstract objects and do not
silently omit direct properties for physical objects.