app-creator/README.md
Kjell Tore Guttormsen dec8048766 docs: skriv README gjennomfort engelsk (ORDRE 52, AAA+ runde 4)
README-LANGUAGE-funnet: 24 norske markorord mot 5 engelske i et repo som er
deklarert engelsk. Brodteksten oversatt, ikke bare ordene -- pre-design-
avsnittets substans (manuell prototype gjennom hele app-creator -> Voyage-
pipelinen for en reell iOS app) er bevart, og det samme er v4.3-Plugin-
Playground-forbeholdet om at flaten ble slettet i Voyage v5.0.0.

Uendret med vilje: H1 (linje 1) og tagline (linje 3) er byte-identiske, sa
README-DESC-matchen mot forge-beskrivelsen fra af921a2 overlever. Headingene
## Install og ## Non-goals er beholdt ordrett -- de er maskin-sjekkede
strenger, lagt til i af921a2 for a lukke org-ops-ERROR.

Ingen release laget. Begrunnelse i STATE.md (local-only): konsumpsjons-
mekanismen for domain-packs/ios-app er snapshot-kopi med absolutt lokal sti
og pack.json-versjon, ikke git-ref, sa en repo-tag tilforer ingenting til den
ene reelle konsumenten; masterplan F2 gjor v0.4.0 til forste tag; og repoet
har null kjorbart innhold (46 filer, alle markdown/data).
2026-08-17 13:35:40 +02:00

2.4 KiB

app-creator

Pre-design pipeline from app concept to Voyage-ready feature briefs — interview, research, architecture, design, constraints, feature derivation, and a per-app HTML status view.

Status: Pre-design. No code has been written yet. Implementation waits on a manual prototype run — one real iOS app driven through the entire app-creator → Voyage pipeline by hand — before any of this is built. See CLAUDE.md for the full context.

Install

No code exists yet (pre-design, see Status above) — there is nothing to install. This section gets real install steps when implementation starts, after the roadmap preconditions in CLAUDE.md are met.

The three-tier system

Tier Plugin Question it answers
1 Voyage How do we carry out this task correctly?
2 app-creator What does the app need, and what is the next brief?
3 app-factory Which app needs me now, and what action does it require?

What app-creator is meant to do

Drive a single app from idea to feature backlog through seven phases: interview → research (optional) → architecture decisions → design system → constraints → feature derivation → one brief per feature. Each phase produces an artifact on the filesystem. The brief phase generates Voyage-compatible markdown files that Voyage /trekplan consumes without modification.

The per-app HTML renders every artifact, shows phase progress and attention, and lets you drill down into the artifacts from each feature's Voyage run (voyage_run_dir + annotate HTML). The patterns are inherited from Voyage's v4.3 Plugin Playground — a historical ancestor; the surface itself was deleted in Voyage v5.0.0.

app-creator does not execute Voyage. Briefs are handed over as files.

Non-goals

  • Carrying out tasks (that is Voyage's job)
  • Executing the Voyage runtime (briefs are a file handover, not a runtime call)
  • Aggregating multiple apps (that is app-factory's job)
  • Replacing Linear/Jira, or assuming any external PM tool (tool-agnostic is a hard invariant)
  • Coordinating teams
  • Running autonomously without a human in the loop

Positioning

Solo-maintained, fork-and-own. Primarily for the author's own work. Issues welcome as signals — no pull requests. No backward compatibility guarantees before v1.0.0.

License

MIT — see LICENSE.