Workspace Root Governance Snapshot

workspace-root-snapshot/ is a version-controlled recovery copy of the three drive-root governance files: D:\AGENTS.md, D:\Development.manifest.toml, and D:\INDEX.md. The files at the drive root remain authoritative — this snapshot exists purely so that if the live root copies are ever lost or corrupted, City Hall's own Git history has a recent, hash-verified backup to restore from.

The snapshot is refreshed by tools/snapshot_root_governance.py, which compares SHA-256 hashes and only rewrites the snapshot (plus SNAPSHOT.toml) when --apply is passed and a file has actually changed. Treat this whole folder as a worked example of what the current, live D:\ drive root looks like — as opposed to the Target Directory Map and Workspace Governance Implementation Plan, which describe an earlier numbered-root proposal.

README.md

# Workspace Root Governance Snapshot

This directory is a version-controlled recovery copy of `D:\AGENTS.md`, `D:\Development.manifest.toml`, and `D:\INDEX.md`. The files at the drive root remain authoritative. Refresh this snapshot with `snapshot_root_governance.py --apply`; do not edit snapshot copies directly.

SNAPSHOT.toml

The hash-indexed manifest recording exactly which source files were captured, when, and with what SHA-256:

[snapshot]
authoritative = false
purpose = "Version-controlled recovery copy of D drive root governance records."
source_root = "D:\\"
refreshed_utc = "2026-07-08T07:37:01.632200+00:00"

[[snapshot.files]]
name = "AGENTS.md"
source = "D:\\AGENTS.md"
sha256 = "20193127ca31c3cefdc0df54ced0ca6c73d57ef50bcdc2cfe596af7dbce969a5"
size_bytes = 5606

[[snapshot.files]]
name = "Development.manifest.toml"
source = "D:\\Development.manifest.toml"
sha256 = "55006747472d3b358c07a2f22b4396ca6b127cd68ffbadede3bebaf615d6ab59"
size_bytes = 3864

[[snapshot.files]]
name = "INDEX.md"
source = "D:\\INDEX.md"
sha256 = "ac10794ecce0c685961c6b3d30feab63faab8dc527bea43cc7d7adb33bab760d"
size_bytes = 87485

AGENTS.md

The live drive-wide agent constitution. This is the actual, current version of the document templated by AGENTS.root.md:

# D:\ Drive Agent Constitution

## Scope and precedence

This file governs work anywhere under `D:\`. Read applicable instructions from the drive root toward the target directory before changing files.

Rules apply in this order:

1. Explicit operator instructions for the current task.
2. The nearest `AGENTS.md` at or above the target.
3. Parent `AGENTS.md` files, up to this document.
4. Canonical standards under `D:\.city_hall`.
5. Project documentation and manifests.

A child may specialize a parent rule for its own scope but must identify the exception. It may not silently weaken safety, integrity, preservation, or release requirements.

## Canonical governance

`D:\.city_hall` is the canonical governance location. Link to standards there; do not scatter copied standards through portfolios or projects.

- [Workspace Governance Standard](../wgs/overview.md)
- [Project Proposal Standard](../pps/overview.md)
- [Command Tool Standard](../cts/overview.md)
- [Desktop Application Release Standard](../drs/overview.md)
- [Website Development Standard](../wds/overview.md)
- [Dataset Development Standard](../dds/overview.md)
- [Service and Infrastructure Standard](../sis/overview.md)
- [Agent Task Standard](../ats/overview.md)

Templates, reference-library copies, migration notes, generated records, and historical manifests are not governing authority unless a canonical standard explicitly says otherwise.

## Required local records

| Entity | Required files |
| --- | --- |
| Governed portfolio or container | `AGENTS.md`, `[DirectoryName].manifest.toml` |
| Individual project | `AGENTS.md`, `[ProjectName].manifest.toml`, `Project-README.md` |
| Project group | `AGENTS.md`, `[GroupName].manifest.toml`, `Project-README.md` |

An ordinary `README.md` may remain the user-facing or ecosystem entry point. `Project-README.md` owns internal project orientation, governance, architecture, operating state, evidence, and handoff context. Link between them instead of duplicating prose.

## Naming and identity

- Use exactly the containing directory name plus `.manifest.toml` for the canonical local manifest; for example, `CTS.manifest.toml` and `CloneCratesio.manifest.toml`.
- Preserve the containing directory's casing and punctuation in the manifest filename.
- Use `Development.manifest.toml` only for the drive root.
- Use Windows absolute paths in manifest path fields.
- Keep exactly one canonical manifest per governed directory. Component/data manifests with another schema must declare a distinct role and must not claim local entity authority.
- Move superseded generic, duplicate, or historical manifests to a documented City Hall migration archive after reconciling useful evidence.
- Expose canonical standards and templates through manifest paths and Markdown links. Windows `.lnk` files, copied standards, and templates are never governance authority.

## Inheritance and classification

Every governed directory declares a class:

- `project`: one independently governed deliverable with its own lifecycle.
- `project-group`: related projects sharing governance and orientation.
- `container`: organization only; it is not independently versioned or released.

Datasets, standards, services, external sources, and archives retain their specific entity kinds but still declare whether the directory behaves as a project, group, or container where needed.

Child manifests inherit parent governance unless they explicitly declare a more specific standard. Local `AGENTS.md` files should contain only local constraints, commands, boundaries, and links needed to specialize the inherited rules.

## Change rules

- Inspect the target, its manifests, documentation, and current version-control state before editing.
- Do not move, rename, delete, archive, or broadly regenerate an entity without explicit operator approval.
- Do not overwrite unrelated or unexplained local changes.
- Record discovered drift; repair it when the task authorizes the affected scope.
- Keep parent and child paths, relationships, and inventories synchronized when structure changes.
- Never convert a template, generated placeholder, or historical copy into authority merely because it is nearby.
- Generated files must identify their generator or source and must not replace hand-maintained authority without an explicit migration.

## Release and integrity rules

- Follow the standard matching the deliverable class and any additional standards named by the manifest.
- Build and verify the actual shipping artifact before claiming readiness.
- Keep versions, hashes, release notes, manifests, and documentation aligned to the artifact.
- State blockers and partial verification plainly; a successful build alone is not a release verdict.
- Preserve provenance and existing evidence unless replacement is intentional and documented.

## Required startup sequence

Before substantial work:

1. Read this file and each nearer `AGENTS.md` down to the target.
2. Read the nearest entity-named manifest matching its containing directory.
3. For a project or group, read its entity-named manifest and `Project-README.md`.
4. Read the canonical governing standards linked by those records.
5. Inspect current source, artifacts, tests, and version-control state appropriate to the task.

If required records are missing, proceed only within the explicit task scope and report or repair the governance gap as appropriate.

The descriptive drive map lives in `INDEX.md` (the workspace-root drive-level inventory, outside City Hall's scope). Do not turn this file into a second inventory.

Development.manifest.toml

The live drive-root workspace manifest — the filled counterpart to the Development.manifest.toml template:

[manifest]
schema = "APTlantis Entity Manifest"
schema_version = "2.4"
manifest_type = "workspace"
canonical_name = "Development.manifest.toml"
last_updated = "2026-07-08"
maintainer = "Herb"

[entity]
id = "development-drive"
title = "D Drive Development Workspace"
kind = "workspace"
class = "workspace-root"
status = "active"
description = "Local development drive containing governed portfolios, projects, shared infrastructure, references, and canonical standards."
tags = ["development", "workspace", "aptlantis"]

[workspace]
root = "D:\\"
primary_governance = "WGS"
city_hall = "D:\\.city_hall"
index = "D:\\INDEX.md"
instructions = "D:\\AGENTS.md"

[policy]
requires_directory_manifests = true
requires_project_manifests = true
requires_project_readmes = true
requires_agent_instructions = true
canonical_directory_manifest = "[DirectoryName].manifest.toml"
canonical_project_manifest = "[ProjectName].manifest.toml"
preserve_legacy_manifests_with_migration_notes = true
manual_review_required_for_moves = true
copy_canonical_standards_into_projects = false

[standards]
wgs = "D:\\.city_hall\\WGS"
sfds = "D:\\.city_hall\\SFDS"
pps = "D:\\.city_hall\\PPS"
drs = "D:\\.city_hall\\DRS"
cts = "D:\\.city_hall\\CTS"
wds = "D:\\.city_hall\\WDS"
dds = "D:\\.city_hall\\DDS"
sis = "D:\\.city_hall\\SIS"
ats = "D:\\.city_hall\\ATS"
aas = "D:\\.city_hall\\AAS"
arhs = "D:\\.city_hall\\ARHS"
aamhs = "D:\\.city_hall\\AAMHS"
aadr = "D:\\.city_hall\\AADR"
sesm = "D:\\.city_hall\\SESM"
neonink = "D:\\.city_hall\\NeonInk"

[[roots]]
id = "city-hall"
path = "D:\\.city_hall"
kind = "standards-registry"
role = "Canonical standards, frameworks, schemas, templates, and governance references."
manifest = "D:\\.city_hall\\010-CITY-HALL.manifest.toml"

[[roots]]
id = "wds"
path = "D:\\WDS"
kind = "portfolio"
role = "Website and web-application projects."
governing_standard = "WDS"
manifest = "D:\\WDS\\WDS.manifest.toml"

[[roots]]
id = "basic"
path = "D:\\BASIC"
kind = "portfolio"
role = "BASIC-family workshop, projects, and reference sources."
governing_standard = "WGS"
manifest = "D:\\BASIC\\BASIC.manifest.toml"

[[roots]]
id = "cts"
path = "D:\\CTS"
kind = "portfolio"
role = "Command tools, automation, APIs, and data-processing utilities."
governing_standard = "CTS"
manifest = "D:\\CTS\\CTS.manifest.toml"

[[roots]]
id = "data"
path = "D:\\DATA"
kind = "portfolio"
role = "Shared datasets, source snapshots, and dataset-producing projects."
governing_standard = "DDS"
manifest = "D:\\DATA\\DATA.manifest.toml"

[[roots]]
id = "drs"
path = "D:\\DRS"
kind = "portfolio"
role = "Desktop applications and related project groups."
governing_standard = "DRS"
manifest = "D:\\DRS\\DRS.manifest.toml"

[[roots]]
id = "dpw"
path = "D:\\.dpw"
kind = "shared-infrastructure"
role = "Shared development runtimes, caches, tools, and infrastructure."
governing_standard = "WGS"
manifest = "D:\\.dpw\\.dpw.manifest.toml"

[[roots]]
id = "library"
path = "D:\\.library"
kind = "reference-library"
role = "Shared reference, documentation, evaluation, and media library."
governing_standard = "WGS"
manifest = "D:\\.library\\.library.manifest.toml"

[[roots]]
id = "sonar"
path = "D:\\.sonar"
kind = "shared-runtime"
role = "Shared SonarScanner CLI runtime."
governing_standard = "SIS"
manifest = "D:\\.sonar\\.sonar.manifest.toml"

[agent]
read_first = ["D:\\AGENTS.md", "D:\\INDEX.md", "D:\\.city_hall\\WGS\\Agent-Startup-Procedure.md"]
authoritative_docs = ["D:\\Development.manifest.toml", "D:\\AGENTS.md"]
known_gaps = ["Project build, test, artifact, and release posture remains explicitly unverified until reviewed per project.", "The former .agents root is absent and intentionally not registered."]
notes = "Entity-named manifests govern the current layout. Superseded generic and historical records are preserved only in documented City Hall migration archives."

Note that this live manifest registers ats, aas, arhs, aamhs, aadr, sesm, and neonink under [standards], and eight portfolio/foundation roots under [[roots]] — a fuller registry than the generic Development.manifest.toml template, which only lists WGS through SIS and a single example root.

INDEX.md

INDEX.md is the full human-readable map of the D:\ drive: purpose, operating model, root-level contract, the hidden foundation directories (.city_hall, .dpw, .library, .sonar), known documentation/manifest drift, and a detailed portfolio-by-portfolio tour of BASIC, DRS, CTS, DATA, and WDS — including per-project purpose, current evidence, read-first order, and handling rules for dozens of individual projects.

At roughly 1,150 lines and 87 KB, it is far too long to usefully inline into a single doc page, and most of its governance-relevant content (root contract, standards map, health model) already appears in the Workspace Inventory, Target Directory Map, and this WGS suite's other pages in condensed form. It is reproduced in full as a downloadable file instead:

Download the full workspace-root-snapshot INDEX.md (saved with a .txt extension so it's served as a plain download rather than compiled as a site page)

Its table of contents:

1. Purpose of the drive
2. Operating model and goals
3. Root-level contract
4. Central documents
5. Central concepts
6. Hidden foundation directories (.city_hall, .dpw, .library, .sonar)
7. Known documentation and manifest drift
8. D:\BASIC — QB64 workshop and incubator
9. D:\DRS — desktop application portfolio
10. D:\CTS — command tools and automation
11. D:\DATA — shared datasets and source snapshots
12. D:\WDS — websites and web applications
13. Scope boundary

:::note Known drift, self-reported Section 7 of INDEX.md is itself a drift ledger: it records, as of the July 7–8, 2026 rollout, specific disagreements between individual project manifests and their current physical paths, versions, and completion percentages (for example, several DRS and CTS project manifests still cite superseded D:\100-DRS\... / D:\200-CTS\... paths, and some report placeholder 0.0.0 versions despite substantial real implementations). This is preserved intentionally per the WGS drift-preservation rule — it is not silently corrected here. :::