Skip to content

Add agent-operable substrate architecture direction#4

Open
simple-agent-manager[bot] wants to merge 4 commits into
mainfrom
sam/use-sam-mcp-tools-01ktgk
Open

Add agent-operable substrate architecture direction#4
simple-agent-manager[bot] wants to merge 4 commits into
mainfrom
sam/use-sam-mcp-tools-01ktgk

Conversation

@simple-agent-manager
Copy link
Copy Markdown

Summary

  • Adds AGENT_ARCHITECTURE.md, a direction document that reframes Chewy from a "deep stack" app generator into an agent-operable application substrate.
  • Core thesis: Chewy's durable moat in an agent world is its machine-readable contract + deterministic engine (the zod schemas and dependency-graph/deploy logic in @gochewy/lib), not the scaffolding agents can already produce.
  • Proposes a layered contract (chewy-app.yml, chewy-interfaces.yml, chewy-runtime.yml, chewy-agent.yml), a plan → contract update → generate → validate → dev/deploy agent loop, a deterministic --json CLI surface, a monorepo-native direction over submodules, and a practical MVP sequence.

Context

Recreates and tracks work from the prior SAM session "Define Chewy agent architecture based on code generation workflows," which produced this artifact but was never pushed. This PR opens it for review/iteration.

Notes

  • Planning/documentation artifact only — no code changes, so no tests were run.

🤖 Generated with Claude Code

raphaeltm and others added 4 commits June 7, 2026 08:39
Reframes Chewy from an app generator into an agent-operable application
substrate: a typed, layered contract (chewy-app/interfaces/runtime/agent)
plus the deterministic dependency-graph and deploy engine in @gochewy/lib,
so code-writing agents can safely plan, generate, validate, and deploy.
Favors a monorepo-native direction over submodules.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…brary

Reframes the moat from a generic "contract + engine" to the concrete vision:
services declare typed dependencies (with modifiers) satisfied through chains
of infra layers (logical->physical->provider, or collapsed by Neon), wired via
explicit requires/provides outputs->inputs mappings. The defensible asset is the
curated library of binding patterns across services x data-services x providers.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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