Travis F WMar 10

I just began an #AMLD repository.
It is a template for Agent-Mediated #LiterateDevelopment methodology.

In a nutshell:
Design documentation and project management should be *on trunk* (or main branch) and must be enough to regenerate everything that has been previously generated with an #AI coding agent. It should be written for humans, except for a log of previously followed plans referenced by closed tickets.

IE the docs are code.

This is not #VibeCoding; this is literate.

Show threadTravis F WMar 15
#AMLD Agent-Mediated #LiterateDevelopment methodology first draft, ready to be tested.
I would love some feedback.
https://hg.sr.ht/~travisfw/amld-method
#agenticCoding
Show threadTravis F W

#Claude likes #AMLD

🙶The methodology aligns well with how I work in several respects:

- Plan-first, human-affirms (wip.adoc review step) matches the principle of checking before acting
- Structured logging (amld/log/, handoff files) compensates well for my lack of persistent memory across sessions
- Declarative design docs as the source of truth is sound — code should reference design, not the other way around
- Ticket discipline gives me clear scope boundaries, reducing drift

Mar 16 at 8:16pmWeb