Status: ACTIVE ACCOUNT-LEVEL CLASSIFICATION
Authority scope: ACCOUNT_LEVEL_LIFECYCLE_ONLY
Machine-readable source: ../ecosystem/repository-lifecycle.json
Lifecycle classifications reviewed: 2026-09-24
Connected owner census reconfirmed: 2026-09-28

• ndrorchestration/DGAF-Framework protected main: 728a5a5ba63e63952f7c3c717239bd4dbdcd92b5.
• Primary current-facing repository state: docs/CURRENT_STATE.md, reconciled through merged PR #1116.
• Accepted architecture authority: PR #1089 architecture governance; PR #1041 is historical/superseded/unmerged.
• This overlay does not alter repository lifecycle classification or promote scientific, efficacy, independent-validation, runtime, or High-Assurance state.

Current authenticated GitHub owner census: 53 repositories, 34 public and 19 private; one archived private repository. These counts supersede the earlier 33-public/20-private snapshot on the same date. This verifies GitHub repository identity and current visibility, not release suitability, secret-history safety or commercial approval.

Game repo renamed AND made public: the stable GitHub repository ID 1372641872 now resolves to To Sail the Starry Sky — source, exact canonical slug ndrorchestration/ToSailtheStarrySky-jrpg. The old aetherwake-jrpg path resolves as a historical redirect, but no live cross-link should represent it as canonical. The different previously proposed slug ndrorchestration/to-sail-the-starry-sky is not the actual repo identity. Main remained 7364d43c202b2186e2d4eb3c752367afe61ee408 during the audit and draft branding PR #358 stayed unmerged.

Public exposure is not release acceptance: Game files, source history, issues and draft PRs may now be publicly visible. Do not claim that save migration, art and code ownership, license compliance, secret scanning, external publication permission, Windows QA, Defender review or player acceptance have occurred. Review them before broader promotion. The game remains INCUBATING in the lifecycle registry.

Public navigation rule: link to repositories that are actually public while explaining evidence and release limitations. Keep remaining 19 private repositories unlinked to avoid misleading external readers. Six historical private references in the table below remain plain text.

Public portfolio/provenance rule: forked upstream/reference repositories are distinct from authored originals. Metadata visibility alone grants no evidence promotion.

Registry freshness clarification (2026-10-23): The canonical ecosystem/repository-lifecycle.json carries generated_at: 2026-10-23 with 53 entries. Current live GitHub verification confirms 53 owner repo identities, including 34 public and 19 private after the game repo rename/visibility change. Classification/lifecycle review dates remain separate from visibility verification.

Public-access note (rechecked 2026-10-23): Entries marked private are retained as unlinked names because external visitors cannot inspect them. The game repo is now public but publication is not equal to product release approval.

Scope: the 27 repositories supplied for this reorganization. This is a navigation and responsibility mapping, not a fresh account census, dependency lockfile, completeness certification, or evidence promotion. Repository metadata and README identities were read on 2026-10-12; lifecycle labels below are retained from the existing account registry, whose review dates remain authoritative.

The supplied account URL is the profile entry point, not an additional repository. The historical concatenated chat-archives / ai-prompt-engineering-portfolio URL has been split into two entries. Private repositories are labeled and are no longer linked as public review destinations. No private artifact contents are reproduced here beyond existing account-level responsibility descriptions.

A runtime dependency requires an exact consumer/source binding, interface or package/version, reproducible composition test, and its own evidence boundary. A navigation link, common pattern, role name, or dashboard view is insufficient. Do not merge AOGA/PPTL/Tektite, Driftwatch/Orbit-Driftwatch, or the evaluation repositories merely because they share a capability group.

The Notion Capability Graph owns workspace composition and discovery records; this account map owns GitHub navigation/lifecycle only. Its inspected record explicitly retains graph completeness as NOT ESTABLISHED and CGAP-12 as blocked. This update does not recount its nodes/edges or insert purportedly verified dependencies.

The DGAF registry is a bounded DGAF projection and explicitly marks its September 16 projection STALE. It must not supersede this account inventory or project-local current state. This reorganization does not refresh runtime identity or promote that registry's status.

Repository nodes and capabilities are different: Governed Repo, Evidence Gate, ClaimGraph, Assurance Profiles, CEP, and Tektite can be capabilities within owning repositories. Adding those names to a capability graph does not require creating or pretending there is a separate repository for each.

• Before: profile navigation emphasized selected projects; this map classified lifecycle without grouping the supplied inventory by capability.
• After: all 27 supplied repositories have one primary navigation group, retained lifecycle, responsibility, visibility, and relationship boundaries.
• Supporting source: repository-lifecycle.json blob 15dfebf088e33185666499ce792a8a0fde4189ba; live GitHub metadata and README reads on 2026-10-12. Lifecycle review dates were not reset.
• Common evaluation contract blob: db1947f3060b6cbdfa2efecea8f72566f9e8bc9f; ACP handoff blob: 6b1059a5f6c89b806174818a06cbf952123f4672.
• Unchanged ceilings: SCIENTIFIC_N_INCREMENT=0; INDEPENDENT_VALIDATION=NOT_ESTABLISHED; CANONICAL_DGAF_EFFICACY=NOT_ESTABLISHED; HIGH_ASSURANCE=NOT_AUTHORIZED.
• Remaining audit work: exact package/import/workflow/runtime dependency census; accepted versus draft integration bindings; graph export and deterministic integrity analytics. None is represented as completed here.

This document classifies how repositories relate to the ndrorchestration account. It does not override repository-local source code, tests, CI, evidence, runtime facts, governance state, scientific state, security claims, or authorization.

Project repositories remain authoritative for their own implementation and evidence. Runtime providers remain authoritative for runtime facts. DGAF may maintain a bounded DGAF-related projection, but it is not the canonical account-wide repository inventory. Cross-repository relationships are descriptive only and never transfer validation or authority.

The September connected GitHub owner census recorded 48 repositories (historical count; not re-established by the scoped October 12 review):

• 47 VERIFIED lifecycle classifications;
• 1 PENDING_REVIEW classification;
• 0 CONFLICTED classifications;
• 5 ARCHIVE_CANDIDATE repositories awaiting the final archive gate; and
• 1 already ARCHIVED repository.

A verified lifecycle means the account-level role is supported by current repository-local documentation and/or GitHub metadata. It does not mean production readiness, scientific validation, security certification, or authorization.

• ACTIVE_CORE — current flagship or strategically important system with a unique responsibility.
• ACTIVE_SUPPORTING — maintained infrastructure, tooling, reference, portfolio, or operational support.
• EXPERIMENTAL — active research/prototype work whose claims remain explicitly bounded by evidence.
• INCUBATING — a real but not-yet-mature project identity.
• HISTORICAL — superseded or predecessor work retained for provenance.
• EXTERNAL_REFERENCE — imported/fork-derived code retained for a concrete active reference purpose.
• ARCHIVE_CANDIDATE — verified inactive/test/obsolete repository proposed for archival after dependency checks.
• ARCHIVED — GitHub-archived repository retained read-only for history.

Review status is separate from lifecycle: VERIFIED, PENDING_REVIEW, or CONFLICTED.

Collabration is the current repository and canonical human-facing product identity. Historical artifacts, deployment/provider records, and immutable provenance may retain the former Intellectro identifier where that identity was recorded at event time; those historical identifiers do not redefine the current repository name.

Gold-star-standards, ai-prompt-systems-portfolio, .github, career-positioning, automation-scripts, ndrorchestration, entrepreneur-hub, dgaf-ops, and agent-control-plane.

These repositories support current work but are not interchangeable authorities. For example, the profile repository owns account-level lifecycle/navigation only, and dgaf-ops does not own DGAF scientific or authorization state.

ai-governance-frameworks, 3d-visualization-hub, junior-apogee-app / AI Evaluation Workbench, phi-calculus-app, sentinel-governance, resumeapex-eval, Driftwatch, Amethyst-Governance-Eval-Stack, Acoustic-mesh, aoga-dashboard, pptl-governance-dashboard, AHG-Zeta-Pell-Autonomous-Lattice, Meshsense, orbit-everyday, and Morse-Orchestration.

EXPERIMENTAL means the project is a current research/prototype track with bounded claims. It does not mean the work is invalid or abandoned.

• AI-Prompt-Engineer — earlier private prompt-engineering portfolio archive.
• ai-prompt-engineering-portfolio — v1 private portfolio predecessor.
• prompt-optimization-library — v0 prompt-optimization baseline archive.
• chat-archives — conversation/protocol/research provenance archive.
• api — dated generic API evidence-status record without an active implementation surface in that repository.

The current public prompt-systems portfolio is ai-prompt-systems-portfolio; the older prompt repositories remain useful lineage rather than competing current portfolios.

• Agentic-Iteration-Metaconcert-Yaml-AIMY- — experiment scaffold whose current purpose is not yet sufficiently documented for a stronger lifecycle.
• SP1 — game-project home whose current identity and implementation are still minimally documented.
• aetherwake-jrpg — private pre-alpha Aetherwake — The Last Solarpunk Airship track with a playable vertical slice and active standalone Windows preview packaging; retained as incubating while the game and delivery path mature.
• coherence-control-benchmark — private AI evaluation/orchestration-control benchmark prototype; INCUBATING with PENDING_REVIEW. The repository README now states the intended identity and evidence boundary; executable verification remains the promotion gate.

The following have passed classification review as archive candidates but have not yet been archived by this lifecycle record:

• cli — only a minimal Go “Hello, Bounty Hunter!” stub and no established current ecosystem responsibility.
• __forktest_1787727107 — disposable fork test of octocat/Hello-World; no operational account references found outside lifecycle-cleanup documentation.
• DGAF-Google-AIStudio — generic AI Studio scaffold; no established current DGAF implementation responsibility or account references outside this cleanup.
• unsloth — upstream-derived Unsloth snapshot with no local authored branch or active account dependency found; preserve Apache-2.0/upstream provenance.
• Soroban-Eas__soroban-sas — contribution-attempt fork whose upstream issue is completed and whose account PRs are closed unmerged; no separate active account responsibility found.

Archival still requires the final dependency/open-work/readback gate. ARCHIVE_CANDIDATE is not equivalent to ARCHIVED.

• gold-star-qa-framework — GitHub archived state is already established; retained for historical Gold Star QA provenance.

The following fork-derived repositories have a concrete retained contribution/reference purpose. Upstream remains canonical, and these forks are not counted as original authored portfolio projects:

Fork provenance and contribution history establish origin and a bounded retention reason only; they do not transfer upstream authority or make these repositories original portfolio projects.

• coherence-control-benchmark — PENDING_REVIEW. The README now reconciles the intended identity and explicit evidence boundary on main. Fresh-checkout install, typecheck, build, and any benchmark-specific verification remain NOT VERIFIED for lifecycle promotion. Keep the repository out of the public portfolio until executable verification completes and the implementation/evidence surface is re-audited.

New ambiguity must be recorded explicitly rather than inferred into an existing lifecycle.

An active repository should be able to complete this sentence clearly:

This repository exists separately because it owns [specific responsibility] and no other repository owns that responsibility.

Repositories that cannot pass this test are candidates for supporting, historical, incubating, consolidation, or archive review. Classification does not require deleting history or merging unrelated code.

A repository may move from ARCHIVE_CANDIDATE to ARCHIVED only after verifying all of the following:

1. it is not the canonical source for an active project;
2. no active mutable deployment, workflow, package, documentation contract, or dependency requires continued development there;
3. useful unique material is preserved or linked;
4. open work is adjudicated or explicitly retained as historical provenance;
5. upstream/external attribution remains intact where applicable; and
6. GitHub archive state is read back after the mutation before the registry is changed to ARCHIVED.

No repository is archived merely to make the profile look cleaner.

The GitHub profile is a curated projection, not the complete inventory. It emphasizes a small set of current authored work and links here for lifecycle detail. External/reference repositories, archive candidates, historical work, and unresolved repositories remain discoverable without being presented as equivalent current portfolio projects.

1. complete executable verification for coherence-control-benchmark foundation PR #1, then reconcile the accepted foundation on main before lifecycle promotion;
2. adjudicate retained open upstream contribution PRs before any related archive decision;
3. execute archival only for candidates satisfying every archive predicate and verify archived=true by readback;
4. continue correcting stale account/repository authority language where found;
5. synchronize DGAF and workspace projections after canonical lifecycle changes without creating competing sources of truth.

The machine-readable registry remains the canonical account-level lifecycle classification surface. This document is its human-readable companion.

A read-only comparison of the 2026-09-24 canonical account lifecycle registry against the authenticated GitHub repository inventory found 53 repositories versus 48 registered entries. Every registered repository was present; the 48 existing entries had no observed visibility or archive-status mismatch. The five identified repositories were subsequently added to the canonical lifecycle registry on 2026-10-23, each with PENDING_REVIEW status. This closes inventory coverage, not implementation or release verification.

This is a current metadata/inventory comparison, not a source audit, merge/admission approval, release determination, or authority transfer. Their repository entry points were inspected and the canonical JSON updated; independent implementation and project-local acceptance remain separate future gates.