Skip to content

feat(plan): full autonomy by default, retire stale model priors - #53

Merged
time-attack merged 1 commit into
mainfrom
release/gstack2-public-beta
Aug 10, 2026
Merged

feat(plan): full autonomy by default, retire stale model priors#53
time-attack merged 1 commit into
mainfrom
release/gstack2-public-beta

Conversation

@time-attack

@time-attack time-attack commented Aug 10, 2026

Copy link
Copy Markdown
Owner

The question budget now defaults to ZERO at every scale — /plan infers, states each inference in one line the user can correct in passing, and goes straight to the plan. Scope/ambition/technical-depth questions are abolished (the model decides and offers a one-line opt-down). Budget above zero comes only from the /plan-tune autonomy dial, which is now actually consumed — users who want more conversation tune it down; nobody configures anything to get the autonomous default.

Also retires the human-era anchors (file-count complexity smells, >15-files→REDUCTION, human-hour estimates, five-question interview gates in spec) and stamps a dated, sourced capability-priors rule into all five plan specialists: never justify narrowing scope by asserting an LLM can't do something — 2026 evidence says pairwise matching is at 92–99 F1 with the error direction inverted vs rule engines; uncertain capabilities get a 30-minute measurement spike, not a product downgrade.

Live-verified against the transcript that motivated this: same prompt, zero questions, ambitious plan with decisions stated and reversible, 5 turns. Free suite green.

🤖 Generated with Claude Code


Summary by cubic

Make /plan fully autonomous by default with a zero-question budget at every scale, so it infers decisions, states them in one line, and moves straight to the plan. Autonomy is opt-down via /plan-tune, and stale file-count/human-hour heuristics are removed in favor of evidence-based capability priors.

  • New Features

    • Chain-wide question budget defaults to zero; decisions are inferred and stated with a one-line opt-down.
    • Autonomy budget comes from ~/.gstack/developer-profile.json using round((1 − autonomy) × 6); absent profile = autonomy 1.0.
    • Consent gates sit outside the budget; if unbundled, skip the action and note it in one line.
    • Allow batching independent questions in one round; still counts per question.
  • Refactors

    • Retired file-count triggers (e.g., “>15 files → reduction”) and human-hour estimates; size by agent sessions + review time.
    • Eng review now flags unjustified structure, not diff size; challenge new components that duplicate existing ones or built-ins.
    • autoplan auto-approves expansions inside blast radius with no new infra or authority boundary; file count no longer a proxy.
    • spec self-answers discovery, marks DECIDED choices, and sizes issues by review-ability, not human build-days.
    • Added dated capability priors across plan specialists: do not narrow scope by claiming model limits; measure uncertain, load-bearing capabilities with a 30-minute spike (~50 labels, 85–90% agreement).

Written for commit 412f88b. Summary will update on new commits.

Review in cubic

Three changes, one judgment surface, interleaved in the same files:

AUTONOMY. The chain-wide question budget defaults to ZERO at every scale:
infer, state each inference in one line the user can correct in passing,
proceed to the plan. Scope, ambition, and technical depth are never
question material. Budget above zero comes only from the person —
round((1 − autonomy) × 6) via the /plan-tune profile, which is now
actually consumed (its observational-only disclaimer was true and is
gone). Goal question inferred, ambiguous → Builder; Builder's five
sharpening prompts became commitments; independent questions batch four
per round; consent gates with nothing to bundle into skip-with-note.
Aligned across all seven budget stamps.

HUMAN-ERA ANCHORS. The eng complexity gate challenges unjustified
STRUCTURE, never diff size; ceo's >15-files→REDUCTION trigger is gone;
autoplan auto-approves by blast-radius + no-new-infra + no-authority-
change instead of a 5-file proxy; spec answers its own discovery
questions and DECIDES design choices instead of interviewing; issues
sized by review-ability, not human build-days; hardcoded human/CC speed
ratios removed as drift-prone.

CAPABILITY PRIORS. A dated, sourced rule in all five plan specialists:
never justify narrowing scope by asserting an LLM can't do something.
2026 evidence: pairwise matching 92-99 F1 with the error direction
INVERTED vs rule engines (3% vs 14% false merges), objective judging at
kappa 0.87, grounded hallucination low single digits. What still fails is
named (subjective preference judging, mega-schemas, small-model
clustering). Uncertain load-bearing capability → keep the ambitious
design, plan a 30-minute spike with ~50 labeled examples and an 85-90%
agreement gate. Measure it this afternoon; don't downgrade the product.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 9 files

Re-trigger cubic

@time-attack
time-attack merged commit 41927ca into main Aug 10, 2026
6 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant