Defined capture curation workflow and docs structure
- Day: 2026-04-20
- Time: 10:30 to 10:40
- Project: Business
- Workspace: WP 1: Strategic / Growth & Development
- Status: In Progress
- Priority: HIGH
- Assignee: Matías Nehuen Iglesias
- Tags: Product-Strategy, Capture-System, Knowledge-Management, Docusaurus, Workflow-Design, Micro-Saas
Description
Session Goal
Clarify the product and documentation architecture for a capture-to-artifact system, with emphasis on the post-capture curation layer and the downstream governance needed to keep the system operational and scalable.
Key Activities
- Compared a generic “AI product” framing against vertical microproducts that can be monetized quickly, and ranked candidate ideas using criteria like willingness to pay, incumbents, and speed to first sale.
- Refined the core product thesis: the real value is not raw capture, but the post-capture curation layer that decides what gets promoted, merged, discarded, actioned, or reused.
- Proposed a dual-axis lifecycle model separating retention state from workflow state to avoid inbox bloat and preserve a clean artifact lifecycle.
- Designed a queue-based triage model with promotion gates, merge rules, selective decay, and human/system roles to keep review lightweight but disciplined.
- Drafted documentation structure changes for Docusaurus, including new pages for Capture Items and Curation & Review, plus sidebar configuration to make the docs navigable and source-of-truth aligned.
Achievements
- Established a clearer product wedge: the system should be validated manually first around curation and reuse, rather than polished capture UI.
- Formalized the downstream governance concept with explicit lifecycle states and review actions.
- Identified documentation additions needed to bridge raw capture and durable artifacts without expanding ontology unnecessarily.
- Produced ready-to-use documentation structure guidance, including sidebar organization for the MAL docs site.
Pending Tasks
- Validate the curation workflow manually with a narrow wedge use case before building a full app.
- Turn the lifecycle and review rules into a minimal schema and operational checklist.
- Decide which vertical microproduct idea has the strongest path to an early paid pilot or first sale.
- Implement or update the Docusaurus pages and sidebar to reflect the new capture governance model.
Evidence
- source_file=2026-04-20.sessions.jsonl, line_number=1, event_count=0, session_id=58c1ffc2926800a30527022a3d9a54898e4d0a1c5221ae9109ea885e7f104157
- event_ids: []