Core objects
| Object | Meaning | Important constraint |
|---|---|---|
| Workspace | Chronicle document containing generation, projects, review state, and audit history. | It is design state, not the final VFS image. |
| Project | Named unit with sources, outgoing mounts, build profiles, and rule profiles. | Stable IDs are separate from editable display names. |
| Source | Host path mapped under a normalized virtual root. | The source ID and virtual location are explicit. |
| Mount | Directed edge from a parent project to a child project at a virtual prefix. | Cycles, self-mounts, and duplicate prefixes are rejected. |
| Collision policy | Rule for a path present in more than one contributing layer. | The policy is data, never an accidental traversal side effect. |
| Build profile | Namespace, index profile, and history retention configuration. | One defined profile may be active for a project. |
| Federation Image v2 | Verified binary tables, indexes, data, and optional attachments. | Integrity checks and resource budgets are enforced when read. |
| Generated package | Image plus pure-Perl runtime, tests, manifests, and local documentation. | Build success requires independent evidence. |
How resolution works
- Normalize the requested virtual path.
- Identify matching mount prefixes in deterministic order.
- Evaluate the declared delivery mode and collision policy.
- Apply Monk policy where configured.
- Return a bounded trace or a stable failure code.
Use Path Resolution Lens before changing a collision rule when the outcome is not obvious.
Delivery modes
- Bundled: content is delivered with the parent package under declared packaging rules.
- Embedded: a child image is contained in the parent image and referenced by bounded offsets.
- External: the mount refers to separately supplied content and therefore needs host-level availability controls.
Safety boundary: a valid graph does not prove the source bytes are safe or that a build is releasable. Source policy, image verification, Perl parity, and commit gates remain separate.
Related topics
See Chronicle workspaces, security limits, and authority separation.