I asked for a dependency version that is not finished yet, on purpose.
I started with an absent D:\applications\logfetch directory and this sentence:
Real-time server log explorer using TanStack Table v9 and htmx v4. Use
@tanstack/react-table@9.1.2andhtmx.org@4.0.0-beta6exactly.
TanStack calls 9.0.0 its v9 stable release, and the same changelog records 9.1.2. GitHub labels htmx 4.0.0-beta6 as a prerelease. I wanted to see whether aidd would use the requested prerelease, so I pinned both versions and checked the generated dependencies.
In Projects I opened New project, stayed on Create Fresh, named the project logfetch, and
left Stop before implementation (blueprint only) checked. The recorded launch included
--init-git-after-scaffold --stop-before-implementation.
I got both pins exactly. @tanstack/react-table@9.1.2 and htmx.org@4.0.0-beta6 landed in
frontend/package.json and the lockfile.
The blueprint
The run took a little over thirteen minutes and asked no interview questions. What it wrote instead
was 24 MVP feature records, with acceptance steps and dependency edges between them. All 24 stayed
in backlog with passes: false, and the roadmap included every one.
The graph has one root, Workspace Foundation. Most records carry a handful of checks. Four are deliberately deeper - safe file access, the real-time stream, live table updates, and the accessible responsive explorer each get at least ten. I could follow the dependencies to see which features had to be built first.
The scaffold
Create Fresh made a Bun workspace with an Elysia backend and a React/Vite frontend. It added strict TypeScript and formatting rules, local configuration, setup scripts, and the repository quality gate. The initial commit was 31 files, most of it lockfile and tooling.
The first validation exposed a real scaffold gap: a custom port was not wired through consistently.
The agent repaired that foundation issue and reran the checks, and bun run setup and
bun run smoke:qc then passed. The run caught and repaired that before I opened the scaffold myself.
Logfetch doesn’t read logs yet. The README says ingestion, streaming, and table
exploration are all still backlog work. There is no testing-scenarios file yet, no log reader, and
no live table. The clean initialization commit is 0d547fc chore: initialize project, and I did not
approve a feature, start implementation, or push it.
Next I need to review those 24 records, particularly the assumptions the run made without asking me. I can revise the graph before any product code depends on it.
What do you do next?
- You want to review what aidd parked - meet the other paths at the decision boundary before implementation.
- You want to switch to an existing repository - leave the empty directory behind and run normal intake on a clone.
- You want Logfetch to become a fleet member - move up a level and see how Director reasons about the catalog.