One decision.
Everything else is audit.
Council can think in depth. You should see the recommendation, confidence, next move and what would change our mind — then open the reasoning only when you want it.
What Council can actually see
Founder briefing
Five rules Council does not break
A = tool-verified, B = repo-asserted, C = externally validated, D = inference.
Related repos become venture families before they compete for priority.
Critic must attack the leading consensus before the decision closes.
The Chief speaks after the challenge and chooses one priority.
Every major decision states confidence and what evidence would reverse it.
Latest activity
See what exists. Then decide what deserves to become a company.
Repository metadata is evidence of activity and technical shape. README claims are not automatically external proof. Council keeps that distinction visible.
How to read Council's claims
API state, timestamps, file existence and machine-observed facts.
Claims written in descriptions or READMEs; useful, not independently verified.
Real customer, revenue, usage, deployment or independently checked source proof.
Venture clusters, impact, buyer, pricing, fit, ranking and hypotheses.
Decision first · audit on demand
Distinct roles, explicit authority.
Specialists should enter because they add unique value, not because more voices look impressive.
Remember decisions and lessons — not stale dashboards.
Live system state is refreshed from tools. Memory is reserved for durable context.