Nicolas Martignole (Le Touilleur Express), co-written with **GLM-5.2** and **MiniMax-M3**, publishes **« The Token Manifesto »**: a pastiche of the **Manifeste Agile** (2001) transposed to the LLM era, where the unit of value is no longer the engineer-hour but the **token**. Four values: *short system prompts over clever system prompts*, *one clear example over three paragraphs of explanation*, *iterating in small steps over dumping the whole spec at once*, *outputting in a defined format over letting the model freestyle*. Twelve principles subvert those of Agile one by one — "simplicity, the art of maximizing the amount of work **not done by the model**," "self-organizing teams that spot repetition and document it once," "regular reflection **before the monthly bill arrives**." Beneath the humor ("staring at a usage bar nervously") lies a serious thesis: the real economic constraint of AI-assisted dev is no longer velocity but the **token budget** and the **context-window economy**. Two punchlines close the text: **« You don't have a prompt problem. You have a context-window problem. »** and **« Everyone's a prompt engineer until they run out of monthly quota. »** Worth noting, the meta wink: a manifesto on token frugality co-written *with* models.
SFEIR analysis note that reexamines the software architect profession in the age of generative AI through the framework of **Gregor Hohpe** (*The Software Architect Elevator*). Central thesis: the « **Oracle** » architect — the holder of supreme knowledge dictating rules from an ivory tower — is obsolete, since AI generates code and proposals on demand; the modern architect becomes an **intelligence amplifier (IQ Amplifier)** who provides teams with mental models, business context, and decision tools to leverage AI while ensuring system coherence. The document breaks down the impact **floor by floor of the "Architect Elevator"** (Enterprise / Solution / Platform / Software architect) and argues for **Domain-Driven Design (DDD)** as an essential safeguard: the **ubiquitous language** serves as the basis for *system prompts* (a domain dictionary injected via `.clinerules`/templates, reducing hallucinations and business misinterpretations) and **bounded contexts** restrict the scope entrusted to AI to maximize generation reliability. Conclusion: AI is not a threat but a catalyst that relieves the architect of technical grunt work to emphasize synthesis, strategic vision, modeling, and the human link between tech and business. Domain: software architecture, the architect's role, DDD, structured prompting, enterprise AI governance.
#Software architect#architect's role#generative AI
Anthropic - Measuring political bias in Claude - Even-handedness 94-95% - Paired Prompts method - Open-source evaluation - Character training - Comparison of 6 models - Neutrality system prompt - GitHub