CONTENT REVIEWED OCTOBER 5, 2026 AGAINST CANON · STATUS MAP, NOT LIVE TELEMETRY
The Registry
The estate is more than its showcase. This registry includes the projects and supporting workstreams identified in the reviewed records, including FORGE, PMBOK, the Market Heatmap and Phoenix. It separates current publication work, offline foundations, proposed rebuilds and historical components. Listing a project does not imply that it is complete or running.
Coverage is the public-safe inventory reconciled September 16, 2026 and re-reviewed against canon on October 5, 2026. It is not a census of every private archive or live workflow. Private details remain private; missing evidence remains visible. Inquiries: ashes2echoes.platform@gmail.com.
Published page ≠ operational product. Offline tests ≠ live enforcement. Documented design ≠ completed implementation. Historical screenshots ≠ current data. Unknown does not mean failed.
Free, MIT-licensed software you operate locally or on your own hosting. Explore AI releases, selected workflow-fit reviews, developer changes, and documented version/access history. Select providers for stack-relevance flags; optional exact-product profiles stay in page memory.
No model-provider account is needed to browse. Users fund any hosting, model access or separate collection services they choose. The shared catalog and dated snapshot do not include a guaranteed update service; an independent collector is not bundled. Cost scenarios are hypotheses, not measured savings. Coverage and predecessor history remain partial.
Entry updated September 21, 2026. Tests, review limitations and the separate demonstration's deployment status are documented in the repository. This is not a vulnerability scanner or production endorsement.
FREE SOFTWARE · USER-OPERATED
Portfolio Evidence Pack
Three reviewable examples: résumé-sourced program delivery, offline decision-contract tests, and measured website-release checks. Newly assembled summaries include original code excerpts, test outputs, source URLs and limitations. No login is required for these PDFs.
Reviewed 2026-10-05 against canon. Status words follow one ladder. BUILT means the code or document exists. WIRED means it is connected to a live path. PROVEN means it was shown working with a retained receipt. Merged is not accepted or enforced. None of these controls has independent installation acceptance.
Estate Console (thin client)
A members-only console at app.ashes2echoes.com, with Supabase sign-in and an estate server function (desk-bff). A new member needs a one-time code that the Principal approves; the code is valid for 24 hours. Its status readouts either name their source and as-of time or say UNVERIFIED or NOT BOUND. A checked model answer through the console has not been demonstrated.
WIRED · MEMBERS ONLY · CHECKED ANSWER NOT PROVEN
Enforcement Contract v1.3
Adopted on 2026-10-03, by Principal instruction, as the starting point for estate governance. The contract says v1.3 itself has not been red-teamed, and that a rule may be called enforced only after its tests pass on a bound implementation.
BUILT · ADOPTED · NOT BOUND
Class D Claim Gate
A claim gate and test harness, merged on 2026-10-04 as an unbound candidate. It is not connected to any live path and enforces nothing in production.
BUILT · UNBOUND
Boot Loader v2.8 & Metatron Boot Service
A session boots by verifying signed Ed25519 receipts from a read-only Metatron boot service, matching governance files to their pinned hashes, checking every connector against the registry, and reading the Phoenix carry-forward. The service has no action, approval or trading tool. Installation acceptance: NOT ACCEPTED.
Claim-integrity and task-contract work: make a request's scope, evidence, refusal conditions and residual uncertainty inspectable before accepting an output.
The documented foundation includes a deterministic gate harness and synthetic fixtures. The rebuild brief targets inquiry, evidence cards and output contracts. This registry release does not rerun the harness or establish model-performance gains, a live cockpit or estate-wide enforcement.
Program-management tooling concept covering opportunity gates through project close, dependencies, review criteria and artifact traceability.
A project page and preserved interface screenshot exist. A members-only build now runs in the estate console, under a first-pass standards review, not a certification. An external project completed end-to-end, current integrations and automated enforcement have not been demonstrated. The next proof is a traceable project lifecycle, not another screenshot.
Session continuity, preservation and reconstruction handoffs: carry forward the right context, distinguish source history from current authority, and make resumption reviewable.
Protocol and preservation records establish the documented workstream. They do not establish archive completeness, successful live restoration or current workflow enforcement.
Research view for sector movement, relative volume and source timestamps. It is now built as a members-only console view (October 2026). It has no order path and is not a trade-control authority.
BUILT · MEMBERS ONLY · NO ORDER PATH
CIL → Evaluator → Card → PEARL
Offline decision-evaluation, risk-checking, card-identity and PEARL handoff contracts merged September 16 in a2e-platform PR #15. Runtime wiring, approved trading policies and broker execution are not established by this milestone.
Accumulation, stress, and regime-observation notes that may inform research dashboards after fresh source binding and validation.
SOURCE-OF-RECORD NEEDED
Macro / Liquidity Tripwires🔒 PRIVATE DETAIL
Draft trigger concepts for market-context review. Must remain research-only unless independently validated and approved.
DRAFT · VALIDATION PENDING
Paper Validation Records🔒 PRIVATE DETAIL
Historical paper-trading and review records. Useful as evidence, but not a current performance claim without a source-stamped ledger.
HISTORICAL EVIDENCE
GOVERNANCE & OPERATIONS
Ghost Recon Ops Board🔒 PRIVATE DETAIL
Operations-board concept for lanes, dependencies, closure criteria, review status, and evidence-first task tracking. Visual and workflow pattern should be preserved.
REBUILD CANDIDATE
Lane-Agent Working Notes🔒 PRIVATE DETAIL
Historical and draft material for coordinated agents and lane work. Requires SERAPH containment review before reuse.
HISTORICAL · REVIEW REQUIRED
A2E Definition of Done Standards🔒 PRIVATE DETAIL
Control standard for deciding when work is actually complete. Current rebuild target, not a blanket proof that all artifacts already meet it.
SOURCE-OF-RECORD TARGET
Acceptance-Test Protocol🔒 PRIVATE DETAIL
Pass/fail review pattern for evidence, refusal conditions, and falsification checks. To be normalized before live reuse.
DRAFT · NORMALIZE
Secret Rotation Runbook🔒 PRIVATE DETAIL
Credential-rotation and connector-cutover planning. Secrets are never public and secret-bearing artifacts are treated as defects to remediate.
P0 HARDENING
Principal Runbook🔒 PRIVATE DETAIL
Operating instructions for approvals, escalations, and human decision points. Must be reconciled with SERAPH rebuild authority.
REALIGNMENT REQUIRED
Estate Rebuild Plan🔒 PRIVATE DETAIL
Sequenced rebuild plan for documentation, access rails, FORGE, CIL, Supabase, GitHub, and workflow governance.
ACTIVE REBUILD
PLATFORM & ARCHITECTURE
Heatmap Architecture🔒 PRIVATE DETAIL
Proposed data-provenance chain for market dashboards. Must prove source, timestamp, transform, and display path before any current claim.
VALIDATION PENDING
Rails & SOP Design🔒 PRIVATE DETAIL
Refusing-rail pattern: rules should terminate in gates that can say no, log why, and prevent action when evidence is missing.
REBUILD PRINCIPLE
A2E Estate Index🔒 PRIVATE DETAIL
Component inventory and maturity map. Requires ongoing reconciliation as repositories, documents, and workflows are scrubbed.
INVENTORY IN PROGRESS
Boot and Lane Instructions🔒 PRIVATE DETAIL
Session and lane instruction material. Current authority must come from source-stamped reads, not legacy names or old prompt claims.
Gap register for rebuild work, including documentation closure, access rail hardening, workflow review, and source-of-record decisions.
ACTIVE REBUILD
RELATED RESEARCH COMPONENTS
These named components belong in the estate map, but are not all newly commissioned or currently running. The platform source inventory (access note) explicitly describes a legacy prototype and rebuild workspace. The protocol index (access note) records related designs; its historical version and operational claims are not adopted here.
HUNTER
Market-scanning research covering flows, filings, earnings and candidate discovery. Source modules are documented in the platform inventory; current feed quality, scan freshness and decision integration need separate verification.
LEGACY SOURCE · REVALIDATION NEEDED
SENTINEL
Portfolio-monitoring research and legacy alert logic. Broker positions, alert delivery and protective action are not established by the existence of this module.
LEGACY SOURCE · NOT BROKER PROOF
GABRIEL
A workflow component for overnight watch of market events. It is not an agent seat. The documented component is not proof of a currently scheduled watch or delivered alerts.
WORKFLOW COMPONENT · RUNTIME UNKNOWN
Signal Engine
Signal-generation and market-watch architecture recorded in the protocol inventory. Current scheduling, source lineage and consumer wiring must be demonstrated before describing a live signal service.
ARCHITECTURE RECORD · WIRING UNVERIFIED
AIORA / Trading Research
Historical trading-research umbrella and related strategy records. Retained for lineage, not as a claim that legacy rules are current policy or that any strategy has established an edge.
HISTORICAL RESEARCH · POLICY REVIEW
Backtesting & Setup Assessment
Historical simulation and paper experiments for evaluating one precisely defined setup at a time. Includes comparable samples, execution-friction assumptions and contradictory evidence.
Legacy backtest source and paper records are distinct from a validated strategy. Data quality, leakage, sample reliability and out-of-sample behavior must be assessed for each experiment.
RESEARCH WORKSTREAM · NO PERFORMANCE CLAIM
IRONCLAD
Documented position-management and risk-rule work. A rule document is not proof that an order path enforces loss limits, exposure caps or protective orders.
POLICY RECORDS · ENFORCEMENT UNVERIFIED
TOOLS, INFRASTRUCTURE & PUBLICATIONS
METATRON & Lane Governance
Orchestration, role boundaries and source-stamped instructions. Includes the ongoing reconciliation of boot, review and human-authorization contracts; historic agent names do not establish current authority.
Prototype migration of workflow components into Python services, tests and reporting adapters. Repository structure is available; deployment health, provider integrations and operational parity are not implied.
Interactive cockpit and UI-design work. A preserved website prototype and a documented design-skill entry establish the project; they do not establish current estate telemetry or functioning control paths.
Existing apparel storefront project preserved in the website source. Current commercial activity, checkout, fulfillment and any legacy donation claims were not validated for this registry release.
Long-form methods, specifications and practical reference material associated with FORGE. Book and field-manual records are documented; inclusion does not imply a finished or independently reviewed publication.
Recruiter-facing publication work: the Principal-approved résumé, readable project pages and reviewable portfolio artifacts. Public document downloads are PDF-only.
The request form sends requests to the estate server, which stores them for Principal review and sends no email. An approved requester receives a one-time code from the Principal and creates a login in the console. The older access-code gate and the n8n intake forms are retired.
Automated email delivery and any Telegram approval integration are not in use.