Ideas have histories.
A mechanism can grow inside a system and become useful on its own. Follow those connections without losing the original work.
This catalogue brings together integrated snapshots, focused extractions, public continuations, and worked experiments. A family can share a source project, describe an integration, or collect peer adapters. The relationship is named where it matters.
Public catalogue edition · September 2026. The earlier source dates below describe particular experiments, not the age of every public package.
See the documented source dates ↓Builder, Factory and the Python Foundry
Builder and Factory orchestration experiments led into an integrated Python workbench. Its package compiler, Assembly, runner, chatroom and graph-import mechanisms now have focused public presentations; the Codex context tools preserve adjacent historical chatroom work.
Public Builder/Factory/Fungus packages are adapted continuations, not the entire original workspaces. The family does not prove each public package imports another.
Browse this family →- Agent Assembly RuntimeFocused extraction
- Agent Chatroom LedgerFocused extraction
- Builder PrototypesPublic continuation
- Capability Graph ImporterPublic continuation
- Agent Foundry Blueprint CompilerFocused extraction
- AI Software Factory PrototypePublic continuation
- Fungus ObservabilityPublic continuation
- Materialized Task RunnerFocused extraction
- Python Agent Foundry WorkbenchIntegrated source snapshot
- Codex Session Transcript ExporterPublic continuation
- Message Version Bundle BuilderFocused extraction
Trace the connections and sources
The standalone boundary has documented public adaptations; this is not a promise of current drop-in interchangeability.
The standalone boundary has documented public adaptations; this is not a promise of current drop-in interchangeability.
No installed-code dependency is claimed.
Rebuilt from the historical script; the public interface now emits a plan.
The standalone boundary has documented public adaptations; this is not a promise of current drop-in interchangeability.
The standalone boundary has documented public adaptations; this is not a promise of current drop-in interchangeability.
The linked public package is an adapted representative, not the entire historical source tree.
The linked public package is an adapted representative, not the entire historical source tree.
A documented historical purpose; current direct import/consumption compatibility is not established.
A documented historical purpose; current direct import/consumption compatibility is not established.
- Agent Assembly Runtime: origin and package boundary ↗
- Agent Chatroom Ledger: origin and package boundary ↗
- Builder Prototypes: origin and package boundary ↗
- Capability Graph Importer: origin and package boundary ↗
- Agent Foundry Blueprint Compiler: origin and package boundary ↗
- AI Software Factory Prototype: origin and package boundary ↗
- Fungus Observability: origin and package boundary ↗
- Materialized Task Runner: origin and package boundary ↗
- Python Agent Foundry Workbench: origin and package boundary ↗
- Codex Session Transcript Exporter: origin and package boundary ↗
- Message Version Bundle Builder: origin and package boundary ↗
Skeleton and the ownership rebuild
The later TypeScript Skeleton keeps the integrated workbench. Package, agent-policy and execution boundaries can also be inspected separately, while Seven Ownership explains the architecture and its application.
This family follows the later TypeScript implementation. The older Python graph-editor generation and the current Rubric Rumble implementation are separate.
Browse this family →- Agent Workflow GovernanceFocused extraction
- Bounded Execution LedgerFocused extraction
- Capability Package WorkbenchFocused extraction
- The Seven Ownership ArchitectureWorked architecture method
- SkeletonIntegrated source snapshot
Trace the connections and sources
The parent implementation remains present. The relationship is provenance, not a package-manager dependency.
The parent implementation remains present. The relationship is provenance, not a package-manager dependency.
The parent implementation remains present. The relationship is provenance, not a package-manager dependency.
Normative law, dated audit conclusions and current code are different evidence types.
Carries questions forward; not a file-for-file port and not a statement about every historical Skeleton generation.
Transcript evaluation and Rubric Rumble
The archived evaluator retains the wider console experiment. Provider evidence and governed changes are focused extractions; Rubric Rumble preserves its tournament core and develops a standalone evaluation workflow.
Design ancestry through the broader platform line is documented, but no full chronological chain or current Skeleton code dependency is established. The replay is synthetic.
Browse this family →- Governed Change WorkbenchFocused extraction
- Model Provider Compatibility LabFocused extraction
- Rubric RumblePublic continuation
- Transcript Model EvaluatorPreserved research case
Trace the connections and sources
See the integrated setting from which this independently useful mechanism was separated.
See the integrated setting from which this independently useful mechanism was separated.
The standalone desktop and preparation workflow are new portable implementations inspired by the original evaluator; they do not depend on its desktop application.
Documented adaptation of request/response and usage/rate ideas; not an external runtime dependency.
Transcript planning and reviewed GitHub publication
The planning workbench remains an inspectable historical case. Its GitHub Projects publishing helper has a standalone reviewed-plan interface.
The parent desktop publishing handoff is deferred; the standalone publisher does not make that handoff implemented.
Browse this family →- GitHub Project Draft PublisherFocused extraction
- Transcript to GitHub ProjectsPreserved research case
Trace the connections and sources
The parent desktop handoff is deferred; the helper has its own complete reviewed-plan interface.
Conversation source, migration and Discord archives
Conversation Engine owns the source and transformation vault. A separate ChatGPT toolkit can feed it; Discord Engine reads it and plans an archive. Topology Reconciler isolates planning mechanics from the Discord system.
Feeder and consumer links describe integration, not shared-code ancestry or delivery inside Conversation Engine.
Browse this family →- ChatGPT Export Archive and Migration ToolkitFocused extraction
- Discord Topology ReconcilerFocused extraction
- Conversation EngineIntegrated source snapshot
- Conversation Archive for DiscordIntegrated source snapshot
Trace the connections and sources
Interoperation is explicit; it is not code ancestry or a mandatory dependency for inspection/extraction.
The smaller package re-expresses the retained planning mechanics through a new in-memory contract.
A configured source integration, not a shared-code ancestry claim.
Persistent Discord RPG and its reusable mechanisms
The campaign application remains available. Character rules and durable interaction state have focused platform-neutral extractions with their own hardening.
The extracts are adapted interfaces; neither alone is the entire bot.
Browse this family →- Persistent Discord RPGIntegrated source snapshot
- Persistent Interaction StateFocused extraction
- RPG Character RulesFocused extraction
Trace the connections and sources
The extract contains new neutral interfaces and hardening; the original integrated application remains represented.
The extract contains new neutral interfaces and hardening; the original integrated application remains represented.
DnDGraph import and dice extraction
The ETL package and the pure dice extractor expose distinct parts of the same DnDGraph experiment.
A shared source experiment is documented; a current package dependency is not.
Browse this family →- Dice Expression ExtractorFocused extraction
- D&D 5e Graph ETLPublic continuation
Trace the connections and sources
Shared source experiment; not proof of current code dependency.
Atlas kernel and domain-pack authoring
The kernel supplies the graph and work/evidence machinery. The SDK isolates pack authoring and validation, while the kernel retains its validator.
The private atlas and its personal domain packs are excluded; both public examples are synthetic.
Browse this family →- Atlas Domain Pack SDKFocused extraction
- Atlas KernelIntegrated source snapshot
Trace the connections and sources
The full kernel retains the validator and stays self-contained.
Personal dashboard and source census
The dashboard preserves its first interface and census slice. Provenance Inventory exposes the same source-census laws as a separate utility with an explicit output directory.
A working census does not establish the dashboard proposal for recommendations or semantic indexing.
Browse this family →- Provenance InventoryFocused extraction
- Personal Intelligence DashboardIntegrated source snapshot
Trace the connections and sources
The parent retains its census implementation; the extract changes the output boundary.
Two usage-display adapters
Codex and Ollama display adapters share a visitor purpose and repository while retaining their distinct APIs and screen assumptions.
Two sibling source scripts were packaged together. Neither is documented as derived from the other.
Browse this family →- Usage CaptureRelated adapters packaged together
Trace the connections and sources
Dates with their context.
These are the dates stated in the current origin documents. A source subsystem's date is not a publication date or a complete project timeline. Missing dates stay unfilled; a snapshot label does not tell us whether development is paused.
- June 2025Builder Prototypes
Historical Builder spine/telephone experiment; not the public continuation publication date.
Source ↗ - June 2025Discord Activity Privacy Core
Historical TypeScript/Discord.js source experiment; not the public continuation date.
Source ↗ - September 2025Conversation Target Tagger
Historical chronological target script.
Source ↗ Private archive investigation containing the Chronicle dashboard.
Source ↗- February 2026Persistent Discord RPG
Its character subsystem is documented for this month; the full project start date is not established.
Source ↗ - February 2026RPG Character Rules
Historical RPG character subsystem from which this was extracted.
Source ↗ - March 2026Architecture Difference Case Study
Creation of the controlled comparison working tree.
Source ↗ - March 2026Governed Change Workbench
Historical Transcript Model Evaluator change_workbench subsystem.
Source ↗ - March 2026Transcript Model Evaluator
Its change_workbench subsystem is dated March 2026; not a date for every evaluator generation.
Source ↗ - April–June 2026Python Agent Foundry Workbench
Stated period in which the historical Python working tree was built.
Source ↗ - May 2026Manifest File Relocator
Historical mover.py script.
Source ↗ - June 2026Agent Chatroom Ledger
Historical chatroom backend creation.
Source ↗
Every project is still here.
Some tools have no documented connection to another public package. They remain in the complete catalogue with their own purpose, example, and origin where known.
Browse all 50 offerings →