Context disappears between tools, sessions, and people.
When the next system cannot see the relevant source shape, a human becomes the bridge. Repeated reconstruction is work, not a neutral inconvenience.
Case 004Archived evidence · Context infrastructure
Context
Aggregator
Context is not a blob to dump. It is a shape you decide another system is allowed to carry.
ArtifactElectron / React desktop experiment
CoreAnalyze, filter, scrub, pack
EvidenceArchive scan · 58 files · Nov 2025
Try the shaping idea
From a directory to a context object another system can use.
The original desktop project combined directory analysis, smart filters, token-aware scanning, secret scrubbing, dependency views, history, and vault export. This public-safe instrument makes that pipeline inspectable without reading your machine.
context-os / public reconstructionArchive scan · 58 files
Active stage
SIMULATIONInspect
01 / source selection
Start with the shape of the workspace.
The original tool analyzed a directory before it read the contents. That small pause made the context budget visible before the payload was assembled.
AnalysisPending
FilesUnknown
BudgetHidden
Public boundary Reconstructed from an archive-reported 58-file desktop scan dated November 2025. No local files are read, uploaded, or retained here.
The software-shaped problem
Every context reset makes someone reconstruct the world.
More context is not automatically better context.
Filters decide whether dependencies, tests, configuration, or tooling should travel. The payload is a deliberate view of a project, not an indiscriminate mirror.
Portability needs a boundary.
The source includes secret scrubbing and a vault path. That does not make export safe in every setting; it makes the safety decision visible before the bundle moves.
A bundle is not understanding.
Context Aggregator can preserve files, metadata, token counts, hashes, and structure. It cannot guarantee that the receiving model or person interprets the bundle correctly.
What the source supports
A concrete tool, with a dated evidence boundary.
The available artifact is an archive scan created in November 2025. It is enough to describe the system's shape; it is not evidence of current maintenance, adoption, or production impact.
Electron + React
A desktop shell with a main process, preload bridge, dashboard, scan flow, studio, viewer, and vault surfaces.
Token-aware aggregation
Directory analysis, extension filters, ignore patterns, chunking, language detection, hashes, manifests, and token counts.
Scrub before export
Secret-pattern scrubbing is implemented before a markdown or XML payload is written to disk.
No current-product claim
There is no live repository or fresh runtime proof in this case page. The status stays archived until that evidence changes.
The larger question
What should survive when the session ends?
Context Aggregator is a small answer to a large systems problem: make the boundary between a project and the next intelligence inspectable, editable, and safe enough to challenge.
Context is a design decision