Workflow command center
Turn raw material into reviewable, reusable, implementable work.
LifeHub workflow is not bureaucracy. It is a staged refinement model: capture the material, clarify it, preserve what matters, then move it toward tools, specs, apps, and shipped outputs.
Core rule
Files are the source of truth, not chat.
Important logic, decisions, and outputs belong in the workspace so they remain reviewable, editable, and portable.
Intermediate outputs must be inspectable later, not buried in a conversation.
Work should stay in surfaces that can be revised, reorganized, and improved.
Useful outputs should survive tool changes and remain available in the repo.
Stage progression
The workflow is a guided path, not a rigid conveyor belt.
The preferred movement is raw → structuring → extraction → deduplication → synthesis → assets → specs → app → outputs. Iteration is expected when later work reveals that earlier stages need refinement.
Explore the stage meanings
Raw
Capture source material such as ideas, notes, chats, research, references, and observations.
Structuring
Organize the material so it is labeled, grouped, and easier to work with.
Extraction
Pull out the non-trivial insights, useful facts, and meaningful observations from the structured material.
Deduplication
Merge repeated ideas, preserve unique insight, and flag contradictions or conflicts.
Synthesis
Turn the clarified material into coherent models, frameworks, or structured understanding.
Assets
Convert the models into practical tools such as SOPs, checklists, policies, templates, and operating documents.
Specs
Define workflows, data structures, dashboard requirements, interfaces, and software behavior before implementation.
App
Build software only after the relevant structure and specification are clear enough to implement.
For project-owned implementation, create the full 05_apps/ scaffold at project setup time when the project already has, or is expected to have, an app, software, automation, dashboard, or script stage.
Outputs
Collect final reports, exports, deliverables, reviews, and other artifacts intended for use, handoff, or evaluation.
Movement rule
Do not let stage transitions hide the trail.
As material becomes cleaner, the intermediate work should remain available for review. The point of refinement is clarity, not flattening or losing the reasoning path.
Do not discard useful transitional work just because a later artifact exists.
Later stages may require returning to raw, extraction, or synthesis.
Do not compress away details that may need to be checked later.
Placement map
Put work where its stage and reuse pattern make sense.
The folders are not just storage locations. They signal whether material is raw, reusable, specified, implemented, or ready for handoff.
Raw and early material, including unsorted captures and early project work.
Reusable system methods and operating doctrine.
Reusable operational tools such as SOPs, templates, and checklists.
Requirements, definitions, workflows, and system behavior before implementation.
Shared or cross-project implementation work.
Reviewed final artifacts intended for use, handoff, or evaluation.
Project app workspace
Specs define the system. Apps implement it. Outputs preserve what ships.
If a project is expected to include app, software, automation, script, or dashboard work, create the project-owned app scaffold at setup time.
Use the project's structured 05_apps/ workspace rather than a flat catch-all folder.
Practical aim
Clarity, continuity, and staged refinement.
The workflow exists so valuable work becomes easier to understand, improve, reuse, and implement.