Skip to content

Phase 7: examples/acme-revenue + ADR + architecture doc #8

@cjimti

Description

@cjimti

Part of #1 (project bootstrap, v0.1). Blocked by #7.

Scope: the headline Plexara end-to-end example and the v0.1 documentation set.

Deliverables

examples/acme-revenue/

  • main.go — small, readable end-to-end example against the Plexara ACME demo (https://mcp-demo.plexara.io)
  • README.md — what it does, how to run, what it demonstrates
  • Demonstrates the full path:
    1. Natural-language revenue question
    2. Toolkit classifier narrows to datahub_* and trino_*
    3. Model calls datahub_search + datahub_get_schema to ground itself
    4. SQL safety wrapper: trino_explain first, then trino_query
    5. Result formatted as a small table

Replay test

  • testdata/sessions/acme-revenue.jsonl — recorded session
  • Replay test under the standard suite (no live model, no live network)
  • New examples gate: replay test required (enforced by CI)

Documentation

  • docs/architecture.md — fuller version of the spec's architecture diagram + abstractions tour
  • docs/adrs/0002-provider-model.md — why one OpenAICompatible provider in v1; why channels over range-over-func iterators (spec §6.2). (ADR-0001 is reserved for the toolchain decision landed in phase 1.)
  • docs/prompts/toolkit-classifier.md — the classifier prompt + Plexara toolkit definitions used in phase 5
  • docs/models.md — Qwen3-30B-A3B primary, validated alternatives table

Final v0.1 gate

  • All CI green (build, test, lint, security, codeql, govulncheck, dependency-review, scorecard)
  • Coverage >80% for core/...
  • Cut tag v0.1.0release.yml produces signed binaries + SBOM + SLSA provenance

Out of scope

  • examples/acme-lineage (v0.2)
  • examples/multi-mcp (v0.2)

Branch

feat/bootstrap-acme-example

Spec reference: §6.2, §17, §18 (v0.1) of the bootstrap spec in #1.

Metadata

Metadata

Assignees

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