Skip to content
This repository was archived by the owner on Oct 16, 2026. It is now read-only.

docs(strategy): define repo-native product boundary - #1420

Merged
christso merged 3 commits into
mainfrom
docs/strategy-repo-native-boundary
Jun 19, 2026
Merged

christso merged 3 commits into
mainfrom
docs/strategy-repo-native-boundary

Conversation

@christso

Copy link
Copy Markdown
Collaborator

Summary

Future product decisions now have a single repo-native boundary to anchor on, so AgentV stays focused on real-workspace evaluation instead of drifting into a general dashboard or benchmark-platform surface.

  • add a root STRATEGY.md that defines the target problem, approach, tracks, and non-goals around Phoenix, Harbor, and post-run adapters
  • point AGENTS.md and README.md at that boundary so contributors and coding agents see the intended product shape immediately
  • correct two results-planning docs so future work follows the shipped git-backed results contract instead of stale assumptions

Testing

Not run (docs-only).


Compound Engineering
GPT-5_Codex

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 19, 2026 •

Copy link
Copy Markdown

Deploying agentv with  Cloudflare Pages  Cloudflare Pages

Latest commit: 825129d
Status: ✅  Deploy successful!
Preview URL: https://769f3d28.agentv.pages.dev
Branch Preview URL: https://docs-strategy-repo-native-bo.agentv.pages.dev

View logs

@christso
christso merged commit 2ffa10c into main Jun 19, 2026
8 checks passed
@christso
christso deleted the docs/strategy-repo-native-boundary branch June 19, 2026 02:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant