Skip to content

samwise-x/elon-flow

v0.1.0

A first-principles engineering operating system for deciding what should exist, proving what is true, building the minimum correct implementation, and improving the mechanism that produces the work.

GitHub

Elon-Flow

A self-contained engineering operating plugin built around first-principles reduction, empirical proof, minimal implementation, and recursive improvement of the mechanism that produces the work.

Source projects are research inputs, not runtime dependencies.

Governing sequence

purpose
→ truth
→ question requirements
→ delete
→ simplify
→ find governing constraint
→ build / test / learn
→ accelerate
→ automate
→ improve the production system
↺

The strict five-step engineering algorithm remains:

question requirements
→ delete
→ simplify / optimize
→ accelerate cycle time
→ automate

Skills

  • elon-flow routes nontrivial work without forcing every task through every stage.
  • first-principles decides what should exist and what presently constrains the system.
  • experiment turns observable uncertainty into falsifiable measurement and real-artifact proof.
  • architecture owns domain vocabulary, deep modules, seams, ownership, and test surfaces.
  • implement applies the minimum-implementation ladder after necessity is established.
  • debug builds a red-capable feedback loop, minimizes the repro, tests hypotheses, and proves the root-cause fix.
  • compound turns validated repeated work and recurring corrections into deterministic leverage.

See docs/ownership-routing.md for the canonical ownership contract.

Operating constraints

  • Reality outranks precedent and agent confidence.
  • Observable questions are investigated rather than delegated back to the human.
  • Delete before simplifying; simplify before accelerating; accelerate before automating.
  • Do not create speculative abstractions, dependencies, agents, workflows, or documents.
  • Completion requires evidence at the relevant real output surface.
  • Prefer deterministic mechanisms over repeated inference when both can do the job.
  • A repeated correction should move toward structural enforcement rather than another paragraph of instructions.
  • Stop when the requested outcome is satisfied.

Status

Version 0.1.0 source structure is implemented. Structural validation and routing-evaluation fixtures live in scripts/ and tests/.

Public distribution remains blocked on final source-license and attribution review.