Finished
One meaningful project you completed.
EKHO LAB · SYSTEM SPECIFICATION 01
The Mapping
Engine
A continuity-mapping system that compares real projects, identifies what changes between completion and disappearance, and configures the interface around the evidence.
Trace the process ↓HYPOTHESIS → BEHAVIOUR → RECALIBRATION
Meaningful projects can lose active attentional priority before completion, especially when their state, origin, and progress become difficult to perceive.
This is not a personality quiz. It is comparative project analysis that changes the product.
01 / HOW THE MAPPING WORKS
Compare the conditions.
Find the variable.
Stalled
One meaningful project that lost active priority.
Returning
One project you repeatedly come back to.
Released
Optionally, one you chose to abandon deliberately.
COLLECT
→Contrasting project evidence
COMPARE
→Visibility, re-entry, salience, closure
INFER
→The variable that changed
CONFIGURE
Interface behaviour
02 / CONTINUITY PROFILE
Measure what keeps
the work alive.
Visibility dependence
Does the project stay active when its progress can be seen?
Indexing friction
How hard is it to find the right object, file, or thread again?
Resumption friction
Can the user tell where they stopped and how to re-enter?
Signal competition
How easily does a newer or louder signal replace it?
Expansion tendency
Does the work keep branching faster than it can close?
Completion clarity
Is the finish line concrete enough to recognize?
Origin dependence
Does remembering why it mattered restore momentum?
External accountability
Does another person waiting change completion?
Salience
How much novelty or emotional charge keeps it present?
INITIAL ASSESSMENTHypothesis
→WORKSPACEConfiguration
→REAL USEObservation
→PROFILERecalibration
FROM SCORE TO SURFACE
The assessment must configure the product, not hand over a decorative diagnosis.
- Origins and “why it mattered” remain visible
- No more than three strongly active projects by default
- Automatic “where you stopped” summaries
- Stage-based progress instead of dubious percentages
- A capture lane where new signals do not replace active work
- Meaningful-project resurfacing before disappearance
03 / REALISTIC BUILD SEQUENCE
Plumbing before
the spectacular entrance.
Manual proof
One visual screen: active, stalled, origin, artifacts, where you stopped, and the next visible move.
ROADMAPWorking MVP
Project records, capture inbox, comparison mapper, re-entry summaries, and exhibit pages.
ROADMAPMapping assessment
The finished/stalled interview generates a continuity profile and configures the workspace.
ROADMAPAdaptive behaviour
Observed use recalibrates resurfacing, layout, active-project limits, and presentation.
ROADMAPPublic product
Accounts, themes, privacy, shareable exhibits, integrations, and review views.
ROADMAP
04 / MODEL ROUTING & COST
Use expensive intelligence
only where complexity earns it.
Capture layer
Cleanup, basic tagging, titles, and quick summaries.
$1 input / $6 outputContinuity layer
Project comparison, re-entry summaries, and profile updates.
$2.50 input / $15 outputDeep mapping layer
Initial assessment, ambiguous cases, and architecture synthesis.
$5 input / $30 outputEvidence layer
Search project evidence before synthesis. The model interprets; the database remembers.
$2.50 / 1K file-search callsStandard short-context API rates per 1M tokens, verified July 10, 2026. Storage, hosting, authentication, voice, images, monitoring, labour, and payment processing are separate. Pricing changes; production should read it from configuration, not hard-code it into logic.
CAPTURE→Luna cleans→DATABASE→Retrieval finds→TERRA MAPS→Sol escalates→INTERFACE ADAPTS