The SCRALPT Manifesto

Version 1.0 Context: Generative AI Era

SCRALPT
(Pronounced "Scrapt")

Read in Japanese (日本語)

---

Preamble: From Builder to Sculptor

Software development used to be about building—stacking bricks one by one. But now that Generative AI supplies infinite code at zero cost, our role has fundamentally changed.

We no longer need to build from scratch. Instead, we carve out the essential features from a massive block of raw, generated code. We are no longer Builders. We are Sculptors.

---

Core Values

We redefine traditional development values as follows:

1. Deletion over Creation.
2. Regeneration over Fixing.
3. Sculpting over Planning.
4. Disposability over Consistency.

---

The Three Principles

1. Code is Liability

Code is not an asset; it is a liability. As lines of code increase, so do bugs and maintenance costs. In SCRALPT, progress is measured not by lines written, but by lines deleted.

2. Disposable by Default

Every function is temporary. While interfaces (boundaries) must be preserved, the internal logic is disposable. It should be discarded and regenerated by AI whenever requirements change, rather than refactored manually.

3. Human as Editor

Humans do not write code. Humans focus solely on:

• Seed: Asking the right questions (Requirements).
• Sculpt: Selecting and pruning the output (Decision Making).
• Audit: Ensuring safety and security (Responsibility).

---

The Sculpting Loop (Workflow)

Development proceeds not in time-boxed sprints, but in a continuous loop of Generation and Sculpting.

1. Seed (Define)
   • Define the "Boundaries" and "Intent" using natural language.
2. Ignite (Over-Generate)
   • Let AI generate a massive block of code containing all possibilities, error handling, and variations.
3. Sculpt (Subtract)
   • Humans remove unnecessary features, simplify logic, and carve out the essence.
4. Freeze (Capsulize)
   • Save the working minimum unit as a capsule. This remains valid until the next cycle of destruction.

---

Roles

• Prompt Architect (formerly PM/Architect)
  • Designs the map and crafts the "Seed" for the AI.
• Code Editor (formerly Developer)
  • Possesses the aesthetic eye to read generated code and prune the non-essentials.
• Bot Orchestrator (formerly DevOps)
  • Maintains the pipeline where the AI operates.

---

License

This work is licensed under a Creative Commons Attribution 4.0 International License.