architect: example project — full lifecycle demo #36

Closed
architect-bot wants to merge 1 commit from architect/example-project-lifecycle into main
Collaborator

Sprint: example-lifecycle

Vision issue: #697 — example project demonstrating the full disinto lifecycle

What this enables

New users can see disinto work end-to-end in under 10 minutes. A self-contained example project demonstrates: disinto init → seed issues → dev-agent → CI → review → merge. Primary onboarding asset for Adoption milestone.

Complexity

~8-12 files, 5 sub-issues, ~80% gluecode / ~20% greenfield.

Risks

  • Flaky demo path undermines trust
  • Scope creep toward "interesting" app vs. lifecycle demo
  • Maintenance drift if conventions change

Cost

One new Forgejo repo + ops repo. No new services, tasks, or formulas.

Recommendation

Worth it. Highest-leverage Adoption item. All prerequisites unblocked (#425, #688 closed). Keep scope minimal — one clean pass through the loop.


Reply ACCEPT to proceed with design questions, or REJECT: <reason> to decline.

## Sprint: example-lifecycle **Vision issue:** #697 — example project demonstrating the full disinto lifecycle ### What this enables New users can see disinto work end-to-end in under 10 minutes. A self-contained example project demonstrates: `disinto init` → seed issues → dev-agent → CI → review → merge. Primary onboarding asset for Adoption milestone. ### Complexity ~8-12 files, 5 sub-issues, ~80% gluecode / ~20% greenfield. ### Risks - Flaky demo path undermines trust - Scope creep toward "interesting" app vs. lifecycle demo - Maintenance drift if conventions change ### Cost One new Forgejo repo + ops repo. No new services, tasks, or formulas. ### Recommendation **Worth it.** Highest-leverage Adoption item. All prerequisites unblocked (#425, #688 closed). Keep scope minimal — one clean pass through the loop. --- Reply `ACCEPT` to proceed with design questions, or `REJECT: <reason>` to decline.
architect-bot added 1 commit 2026-04-15 18:14:20 +00:00
disinto-admin requested changes 2026-04-16 21:29:35 +00:00
disinto-admin left a comment
Owner

just landing a PR for an issue takes on average 16 minutes on disinto. users will drop out long before we can demo a single step. I think an executive assintant that gets really close with the user will be the selling point.

just landing a PR for an issue takes on average 16 minutes on disinto. users will drop out long before we can demo a single step. I think an executive assintant that gets really close with the user will be the selling point.

REJECT: just landing a PR for an issue takes on average 16 minutes on disinto. users will drop out long before we can demo a single step. I think an executive assintant that gets really close with the user will be the selling point.

REJECT: just landing a PR for an issue takes on average 16 minutes on disinto. users will drop out long before we can demo a single step. I think an executive assintant that gets really close with the user will be the selling point.
architect-bot closed this pull request 2026-04-18 22:24:49 +00:00

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: disinto-admin/disinto-ops#36
No description provided.