feat(framework): architect stack rationale with PROS/CONS + alternatives (#210)#213
Merged
Merged
Conversation
The web dashboard's edge over the CLI is showing why the AI chose the stack. The architect now returns that rationale, not just a one-line why. - ArchitectPlan gains optional pros/cons/alternatives; agentArchitect and driverArchitect both request and parse them, omitting absent fields so existing producers are unaffected. - New exported STACK_TRADEOFFS gives the architect objective Vike-vs-Next reasons (edge/Cloudflare deploy, renderer-agnostic, ecosystem) so the justification is grounded, not invented. Both architect prompts embed it. - Bootstrap emits pros/cons/alternatives on the architect event and records rejected alternatives to the ledger as rejections. - The dashboard 'Stack & rationale' panel renders pros, cons, and 'Considered instead'. The --fake demo populates them. Part of #209. Closes #210.
suleimansh
added
enhancement
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #210. Part of #209 (the MVP dashboard).
The website's edge over the CLI is showing why the AI chose the stack. Today the architect returns
decisions: [{choice, why}](a one-line why). This makes the stack choice self-justifying.What changed
ArchitectPlangains optionalpros,cons, andalternatives({option, whyNot}). BothagentArchitect(ai-sdk) anddriverArchitect(framework) request and parse them; absent fields are omitted, so existing producers are unaffected.STACK_TRADEOFFSgives the architect objective, reusable Vike-vs-Next reasons (edge/Cloudflare deploy, renderer-agnostic, ecosystem size), so the justification is grounded rather than invented per run. Both architect prompts embed it.Bootstrapemitspros/cons/alternativeson thearchitectevent and records the rejected alternatives to the decisions ledger as rejections, so the ledger shows what was weighed.--fakedemo populates them.Checks
framework --fakeend to end: the architect event carries pros/cons/alternatives; the dashboard page embeds the render path.Not in scope: persistence (#211), live session link (#212).