Every module keeps the formal idea separate from Spencer’s lived implementation. The interface can be playful without pretending a draft standard has been satisfied.
WHAT THE SPEC SAYS
What capability or objective is active?
Maps capabilities, prerequisites, objectives, evidence, lapse, and abandonment while refusing XP, rankings, and composite scores. Capability belongs to an operator, instrument, kit, task, and time; it is not a durable identity trait.
SPENCER’S FIELD IMPLEMENTATION
Quest Log
What I am learning, practicing, revisiting, completing, or deliberately walking away from, with evidence for each state.
SYSTEM GUARD
Draft means draft.
The source is under active development. This page is an interpretation and field notebook, not the normative specification and not a conformance claim.
02 FIELD TOPICS
What belongs here.
These topics are publishing hooks, not formal spec registers. A single field log may belong here and cross-reference several other modules without being copied.
01Main questchannel ready
02Side questschannel ready
03Capabilitieschannel ready
04Practice evidencechannel ready
05Respec retrospectiveschannel ready
03 FIELD LOG
Receipts from real life.
Writing, experiments, intake notes, resources, and journal entries are published once and indexed against every system they touch.
No public field logs yet.
The QUEST channel is wired. Reviewed journal entries, experiments, and resources will appear here without duplicating them across connected systems.
04 LINKED SYSTEMS
Follow the signal.
No module explains a life by itself. These are the nearest crossings, dependencies, and useful next views.