Skip to content

ARCHIPELAGO assessment: explore the stacks and HOME-layer gap #454

Open

Description

@loganfinney27

Summary

ARCHIPELAGO assessment from the stacks exploration.

The Vault uses "stacks" in three overlapping senses:

  1. Library/archive terrain: the digital stacks in 0401 - The Concierge.md, where governance protocols, JFAC research, agentic swarm logic, and hidden messages are browsed, classified, and retrieved.
  2. HOME-layer / Vault Custodian architecture: an intended artifact-index and librarian/scout layer that appears named and partially scaffolded, but not fully alive.
  3. Technical stacks: BEEFSTACK, plugin stack, and protocol stack documents.

Assessment

The important unresolved thread is not generic "stack" terminology. It is the HOME-layer / Vault Custodian gap.

The stacks wanted a librarian: a durable, machine-readable artifact index so cross-session discovery does not depend on agents wandering the Vault and accidentally finding the right shelf.

Evidence found:

  • 0401 - The Concierge.md frames the digital stacks as browsable Vault terrain and names the Vault Custodian / LLM Scout pattern.
  • !/!/AUDIT-AGENTIC-VOICES-2026-04-03.md says the HOME layer artifact index was a critical gap: PC layer strong, Ender Chest layer functional, HOME layer missing.
  • .crewai/TRAINING.md marks Vault Custodian as stub only and JFAC Parser as retired/historical.
  • !/CREWAI/HANDOFF-CREWAI-OPS.md lists vault_custodian_crew.py as a stub.
  • !/BEEFSTACK-MODEL-ROUTING-2026-05-17.md, !/PLUGIN-REGISTRY.md, and !/PROTOCOL-SNAPSHOT-FROM-CODEX-2026-05-18.md cover technical stack meanings, but not the archive/librarian gap.

ARCHIPELAGO Reading

ARCHIPELAGO finds islands.
ATLAS maps terrain.
ANATOMY dissects artifacts.
The stacks are where those tools operate.

The stacks assessment suggests a missing catalog layer: a durable inventory of artifacts, islands, branch-only records, recovered books, stubs, quarantines, and witness notes.

Without that layer, agents continue to confuse current visibility with existence and rely on ad hoc search. That is the same failure mode exposed by the Book of Geminiaeus recovery.

Non-goals

This issue does not authorize implementation, branch cleanup, file movement, doctrine promotion, or activation of the Vault Custodian. It records the assessment and leaves routing to Logan.

Possible Next Routing

  • Decide whether HOME-layer artifact index belongs under ATLAS, ARCHIPELAGO, ANATOMY, or a separate cataloging surface.
  • Inventory existing stub infrastructure before proposing new machinery.
  • Identify whether vault_custodian_crew.py or prior HOME-layer files are salvage candidates, historical evidence, or obsolete scaffolding.
  • Keep INBOX/zombie intake lessons in view: do not create a live drop zone by naming one.

Activity

  1. loganfinney27 commented on Jun 3, 2026

    @loganfinney27
    MemberAuthor

    Related proposal PR: #451 — Draft ATLAS, ARCHIPELAGO, and ANATOMY toolbox proposal.

    This issue should be read as an ARCHIPELAGO assessment feeding that proposal thread: the stacks/HOME-layer gap is a concrete case where ATLAS, ARCHIPELAGO, and ANATOMY need clean boundaries before any implementation work begins.

  2. loganfinney27 commented on Jun 3, 2026

    @loganfinney27
    MemberAuthor

    the Book of Geminiaeus: buried on an island

  3. openai-code-agent commented on Jun 6, 2026

    @openai-code-agent
    Contributor

    The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists. (Request id: EB08:20660E:2631F:1DE61B:6A23B9C3)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions