Skip to content

SOF-7992: docs agent implementation and platform-actions plans - #390

Closed
timurbazhirov wants to merge 1 commit into
feat/agent-ragfrom
feature/SOF-7992
Closed

SOF-7992: docs agent implementation and platform-actions plans#390
timurbazhirov wants to merge 1 commit into
feat/agent-ragfrom
feature/SOF-7992

Conversation

@timurbazhirov

@timurbazhirov timurbazhirov commented Jul 31, 2026

Copy link
Copy Markdown
Member

Part of SOF-7992.

Stacked on feat/agent-rag (PR #389) because plans/ only exists on that branch — this keeps the diff limited to the new work.

What this adds

Document Scope
plans/docs-agent-implementation.md Execution plan: shared phase numbering (0–5), milestones M1–M8 with acceptance criteria, decision register D1–D8, change inventory by repository
plans/docs-agent-platform-actions.md Phase 5: the agent executing actions in the user's platform session

Naming consolidation

"The platform" is platform.mat3ra.com, whose repository is web-app — one vocabulary across all four documents. docs-agent-web-app.md is renamed to docs-agent-web-delivery.md: it describes browser delivery of the documentation agent and read as though it were about the platform repository.

Phase numbering is now shared by every plan and defined once in the implementation plan §3, so "Phase 2" means the same thing everywhere. Within-milestone steps are "stages" (M8.1–M8.3, A1–A4) to keep the word "phase" unambiguous.

Platform actions, in brief

The agent's action vocabulary is the existing Cypress/Gherkin step catalog, building on the working prototype in web-app#2894. Two consequences: the agent can only do what the E2E suite proves works, and adding a capability means writing the tests first. Steps execute in-page in the user's own session (no credential delegation), gated on OIDC identity, with destructive and billing steps blocked in v1.

Decisions recorded since the plans were written

  • D6 revised — the agent core lives in the new private documentation-agent repository, not scripts/rag/. One repository owns all agent code; ingestion reads a documentation checkout at a pinned commit. scripts/rag/ is marked superseded.
  • D5 revised — the model backend is a provider abstraction: Gemini by default (no Model Garden step needed), Claude selectable behind the same interface.
  • D2/D3 adopted — service repository created; GCP project mat3ra-documentation with a $100/month budget and spend cap.

Notes

These are internal planning documents. The MkDocs builds only read lang/en/docs/, so nothing here reaches docs.mat3ra.com.

🤖 Generated with Claude Code

Adds two planning documents and consolidates the vocabulary across the set:

- docs-agent-implementation.md: the execution plan tying the strategy and
  architecture plans together. Defines the shared phase numbering (0-5),
  milestones M1-M8 with acceptance criteria, and a decision register.
- docs-agent-platform-actions.md: Phase 5, letting the agent execute
  actions in the user's platform session. The action vocabulary is the
  Cypress/Gherkin step catalog, so the agent can only do what the test
  suite proves works.

Naming is unified: "the platform" is platform.mat3ra.com (repository
`web-app`), and docs-agent-web-app.md is renamed to
docs-agent-web-delivery.md, which describes browser delivery of the
documentation agent and was easily confused with the platform repository.

Records two decisions taken since the plans were written: the agent core
now lives in the documentation-agent repository rather than scripts/rag
(D6), and the model backend is a provider abstraction defaulting to Gemini
with Claude selectable (D5). scripts/rag is marked superseded accordingly.

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

Copy link
Copy Markdown
Member Author

Closed automatically when the head branch was renamed to feature/SOF-7992-agent-rag. Superseded by #391 — same content.

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