Ho System, Actually Build the software. Develop the judgment.

seed

definition
depth 3/3 − deeper + surface
The Kamae chain 1/6 ← prev next →

The founding document that states a project's problem, vision, constraints, and guiding idea, revised deliberately as it evolves.

The Kamae 1 document: problem, landscape, vision, audience, identity, constraints, scope boundaries, architectural opinion, self-assessment. The parti; a living document revised deliberately with dated notes.

The Project Seed. What it is: The core idea of the project—the philosophical foundation from which everything else follows. The seed captures the problem, the landscape of what exists, the vision, the audience, the constraints, an initial architectural opinion, and honest self-assessment of what the builder knows and wants to learn. It is the product of precedential thinking: research, reflection, and genuine engagement with the problem space.

What it's NOT: A brainstorming dump. The seed is structured enough that someone else—a collaborator, an AI, a future version of yourself—can read it and understand what you're trying to build and why. Enthusiasm is welcome. Messiness is fine in places. But the seed should reflect understanding of the territory, not just excitement about the destination.

What "done" looks like:

Someone reading this document should understand:

  • What the problem is and why it persists (not just that it exists)
  • What exists in the space and where the genuine gap lives
  • What the project does, in plain language
  • Who it's for
  • The builder's initial architectural thinking (opinions, not specifications)
  • What constraints reality imposes (hardware, budget, time, skills)
  • What the builder already knows and what's genuinely new territory

What "done" does NOT look like:

  • Committed technology choices (those are finalized in System Design)
  • File structures or code architecture (too early)
  • Concrete scope (that's the README)
  • A polished narrative (this is working material) […]