Building the Evidence Spine: Phase One Begins

Phase One: What Gets Built

The evidence spine is where PAX:Luma becomes useful before it becomes finished. This phase establishes:

• **Local stores** for originals and derivatives
• **Artifact ingestion** for decks, docs, PDFs, screenshots, and handwritten notes
• **Metadata database** with structured search
• **Obsidian vault writer** for human-readable knowledge
• **Review inbox** for human-in-the-loop corrections
• **First local Meta Llama runtime** for routine transforms

Why This Order

A construct with fancy agency and weak evidence discipline is exactly the wrong order. If the evidence spine is solid, everything that comes after — the committee mind, the action layer, the opportunity engine — has something real to reason over.

The Local-First Principle

The default assumption is that PAX:Luma lives on a local hub you own, with cloud used only where it is clearly helping. A construct that aims at continuity cannot be made entirely out of sessions leased from other companies.

This is a placeholder post. Real engineering updates will document the actual build process.