Migration Notes

migration-notes/ preserves the history of how the workspace's manifest conventions evolved, per the Manifest Conventions preservation rule: superseded records are archived with their original relative path rather than deleted, and every migration event gets a dated note explaining what changed and why.

Entity-Named Live Manifest Migration — 2026-07-08

Decision

Every governed directory uses the exact containing directory name plus .manifest.toml. Development.manifest.toml remains the drive-root exception.

Examples:

• D:\CTS\CTS.manifest.toml
• D:\CTS\CloneCratesio\CloneCratesio.manifest.toml
• D:\.dpw\.dpw.manifest.toml

Preservation

Conflicting live entity-named, generic, and historical records were moved to Legacy-Live-Manifests-20260708 with their workspace-relative paths preserved. No legacy record is a parallel local authority.

The migration tool promoted 63 current governed records, reconciled project version/lifecycle metadata from explicit local evidence, added verification boundaries, normalized paths and inheritance, and updated local document references.

Canonical-link policy

Standards and templates resolve through manifest paths and Markdown links to D:\.city_hall. Six portfolio-root Windows shortcuts were removed. Project artifacts that happen to use .lnk files are not governance dependencies.

Holdings

WDS, CTS, and DRS holding roots now have entity manifests and instructions. Their children remain preserved and excluded from active reporting until explicitly reactivated.

Foundation roots

.dpw, .library, and .sonar were reclassified and normalized. The former .agents root was absent during migration and is intentionally not registered.

Verification boundary

Metadata reconciliation does not imply code, build, test, artifact, or release readiness. Project manifests record those checks separately. No project was promoted to release-ready by this migration.

This is the migration performed by tools/migrate_entity_manifests.py.

Entity Project Manifest Normalization — 2026-06-10

Summary

Normalized live project manifests so governed projects use entity-named files in their project roots, while the generic v2.4 template remains available only as the reusable schema/default pattern.

Batch Scope

The following live project-root manifest files were normalized in this pass (source path, target path, mode, reason):

Source	Target	Mode	Reason
D:\020-LIBRARY\020-LIBRARY.manifest.toml	D:\020-LIBRARY\DocHub.manifest.toml	renamed in place	Preserve DocHub as an entity-named project record.
D:\100-DRS\110-CRYPTO\Aegis\PROJECT.manifest.toml	migration-notes\Legacy-Project-Manifests\Aegis.manifest.toml	archived duplicate	Entity-named Aegis.manifest.toml already existed as the live project record.
D:\100-DRS\120-STORAGE\FileCabinet\PROJECT.manifest.toml	migration-notes\Legacy-Project-Manifests\FileCabinet.project.manifest.toml	archived duplicate	Entity-named FileCabinet.manifest.toml already existed as the live project record.

...and 20 further project roots across 100-DRS, 200-CTS, and 300-WDS (ChromeArchivalPlugin, AptlantisConsole, Structra, Tauri-IT, QB-Winget, ClipboardFilter, CommandWizard, WinTrim, ConversionTools, LangThemeGenerator, CloneCratesio, ArchiveHasher, ReleaseHasher, DatasetPipelines, Training, AnalyzeProjects, PythonDocs, ScriptWriters, Llama, AptlantisLogos, EpicVideos, AAMHS, LinuxGenealogy), each archived under the same migration-notes\Legacy-Project-Manifests\ pattern because an entity-named live manifest already existed or was maintained separately. The full source/target table (30 rows) is preserved at D:\.city_hall\WGS\migration-notes\Entity-Project-Manifest-Normalization-20260610.md; it is abridged here for length.

Verification

• Live project roots no longer contain PROJECT.manifest.toml or project.manifest.toml.
• D:\020-LIBRARY now exposes DocHub.manifest.toml as the project record beside DIRECTORY.manifest.toml.
• Legacy manifest evidence remains available under WGS\migration-notes\Legacy-Project-Manifests\.

Fixed Manifest Naming Migration — 2026-07-07

:::warning Historical trial, superseded Superseded on 2026-07-08 by the permanent entity-named convention documented above. This decision is retained as history and is not current policy. :::

Decision

The current D:\ development layout uses fixed lowercase manifest names:

• directory.manifest.toml for governed portfolios and containers.
• project.manifest.toml for individual projects and project groups.

Identity belongs in [entity], not in the filename. D:\Development.manifest.toml remains the drive-level identity record.

Reason

The workspace accumulated entity-named, uppercase, generic, and historical filenames during earlier numbered-directory rollouts. Fixed names make inheritance and validation predictable while allowing directories to move without renaming their canonical record.

Preservation rule

Legacy manifests must not be deleted merely because a new canonical record exists. Their useful fields must be reconciled into the new record, contradictions recorded under migration gaps, and disposition reviewed manually. Until that review, they are historical evidence and not parallel authority.

Documentation roles

• AGENTS.md: executable modification rules and boundaries.
• directory.manifest.toml: machine-readable portfolio or container truth.
• project.manifest.toml: machine-readable project or project-group truth.
• Project-README.md: internal project orientation, architecture, state, workflows, evidence, roadmap, and handoff context.
• README.md: optional ecosystem-facing or user-facing entry point.

Manifest v2.4 Entity Adaptation

Reason

The earlier default TOML manifest identified itself as APTlantis Project Manifest v2.3 and assumed every governed object was a project. The workspace rollout requires manifests for directories as well as projects.

Change

Version 2.4 introduces a common entity layer:

• [manifest] records schema, version, manifest type, canonical filename, and maintainer.
• [entity] records id, title, kind, class, status, description, and tags.
• Domain tables such as [workspace], [directory], and [project] remain specific to the governed object.

Compatibility

Existing project-specific fields are preserved where possible. Directory manifests now identify themselves explicitly as directory entities instead of being inferred from filename alone.

Pre-Migration Inventory — 20260610-130557

A point-in-time child-count snapshot taken before the 2026-06-10 structure rollout:

Root	Immediate child count
.agents	2
.hf	0
.ollama	2
.program-files	4
.python-installers	270
010-CITY-HALL	19
015-DPW	5
100-DRS	19
200-CTS	16
300-WDS	7
400-DDS	0
500-SFDS	0
960-QB	3
970-DATA	5
980-EVALS	1
990-TESTS	0
LIBRARY	11

Workspace Categorization — 20260610

Summary

Created the numbered category structure under DRS, CTS, WDS, and DATA, then moved clear project/data roots into those categories. Ambiguous top-level service/cache roots were not moved.

Moves (representative sample)

Source	Target	Result	Reason
D:\100-DRS\110-ARCHIVAL	D:\100-DRS\130-ARCHIVAL	moved	Renumber archival category to avoid collision with 110-CRYPTO.
D:\100-DRS\ChromeArchivalPlugin	D:\100-DRS\130-ARCHIVAL\ChromeArchivalPlugin	moved	Archival desktop project.
D:\100-DRS\AptlantisConsole	D:\100-DRS\140-TAURI\AptlantisConsole	moved	Tauri or webview desktop application.
D:\100-DRS\QB-7Zip	D:\100-DRS\150-QB\QB-7Zip	moved	QB-related desktop utility project.
D:\200-CTS\CloneCratesio	D:\200-CTS\220-API\CloneCratesio	moved	API acquisition or reference toolkit command project.
D:\300-WDS\aptlantis_net	D:\300-WDS\310-aptlantis.net\aptlantis_net	moved	Canonical aptlantis.net website project.
D:\980-DATA\cratesio	D:\980-DATA\981-CRATESIO\cratesio	moved	Crates.io data asset.

The full move table (44 rows spanning DRS, CTS, WDS, and DATA) is preserved at D:\.city_hall\WGS\migration-notes\Workspace-Categorization-20260610.md; abridged here for length. See the Target Directory Map for the resulting category numbering.

Follow-Up

• Review generated entity-named project manifests for project-specific metadata.
• Decide whether any remaining service roots such as .hf and .ollama should be redirected into DPW after application-level verification.

Workspace Structure Rollout — 20260610-130557

Summary

Implemented manifest-first workspace structure rollout for top-level governed roots, canonical manifest names, safest root renames, DPW service manifests, and project manifests under project-class roots.

Root Moves

Source	Target	Result	Reason
D:\LIBRARY	D:\020-LIBRARY	moved	Normalize document nexus root numbering.
D:\980-EVALS	D:\970-EVALS	moved	Normalize evaluation root numbering.
D:\970-DATA	D:\980-DATA	moved	Normalize data root numbering.
missing	D:\030-ZONING	created	Initial project scaffolding area.

Legacy Manifest Renames

Source	Target	Result	Meaning
D:\010-CITY-HALL\00-RULES.manifest.toml	D:\010-CITY-HALL\DIRECTORY.manifest.toml	renamed	City Hall root directory manifest.
D:\100-DRS\100-DRS.manifest.toml	D:\100-DRS\DIRECTORY.manifest.toml	renamed	DRS class root directory manifest.
D:\020-LIBRARY\DocHub.manifest.toml	D:\020-LIBRARY\DocHub.manifest.toml	entity-renamed	DocHub project manifest preserved after Library migration; the old generic duplicate was archived separately.

DRS Project Categorization

Source	Target	Result	Reason
D:\100-DRS\Aegis	D:\100-DRS\110-CRYPTO\Aegis	moved	Known crypto/security desktop project.
D:\100-DRS\FileCabinet	D:\100-DRS\120-STORAGE\FileCabinet	moved	Known storage desktop project.

Safety Classification

• Root moves were performed only when the target path did not already exist.
• Legacy manifests were renamed only when the canonical target manifest did not already exist.
• Cache/service roots under .ollama and .hf were not moved; DPW cache locations were documented separately.
• Generated project manifests include known gaps requiring project-specific review.

Archived legacy manifest snapshots (not reproduced)

Two large archive folders exist under migration-notes/ and are referenced above, but are not reproduced as individual doc pages:

• Legacy-Live-Manifests-20260708/ — roughly 25 archived *.manifest.toml files preserving the pre-2026-07-08 directory-manifest state for .dpw, .sonar, BASIC, and CTS subtrees (e.g. .dpw/HF/DIRECTORY.manifest.toml, CTS/AptlantisLogos/AptlantisLogos.manifest.toml).
• Legacy-Project-Manifests/ — roughly 25 archived PROJECT.manifest.toml/project.manifest.toml duplicates for individual projects (e.g. Aegis.manifest.toml, FileCabinet.project.manifest.toml, CloneCratesio.manifest.toml), superseded by the entity-named project manifests described in the Entity Project Manifest Normalization note above.

These are pure historical TOML snapshots with no independent prose content beyond what the migration notes above already describe; reproducing 50-odd near-duplicate manifest files as doc pages would not add information. If a future audit needs their exact contents, read them directly from D:\.city_hall\WGS\migration-notes\ — they remain in the source corpus, just not mirrored into this documentation site.