Skip to content

feat: stackbilt architect — governance layer only, no file generation #5

@stackbilt-admin

Description

@stackbilt-admin

Summary

Rework stackbilt architect to use @stackbilt/scaffold-core/governance directly, producing threat model, ADR-001, ADR-002, and test plan without generating any project files. Zero network, zero inference.

Blocked on: Stackbilt-dev/charter#215.

Current behaviour

stackbilt architect calls POST api.stackbilt.dev/engine/build and caches to .charter/last-build.json. It is anonymous but still makes a network call.

Target behaviour

stackbilt architect "my intention"
  → classify intention locally
  → generate threat model, ADRs, test plan
  → write to .ai/ (or stdout with --stdout)
  → cache classification to .charter/last-build.json for stackbilt scaffold

Fully offline. The governance documents are the architecture decision — no files, no wrangler.toml, no worker.ts. Run stackbilt scaffold to materialise the code from the cached build.

Companion issue

Fix stackbilt scaffold to read from last-build.json correctly after both architect and run — see separate issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions