Skip to content

chore(api): AIN-243 · purge sweep · retire AAMC vocab from code surface#69

Merged
hizrianraz merged 1 commit into
mainfrom
chore/ain-243-purge-sweep-api-v2
May 23, 2026
Merged

chore(api): AIN-243 · purge sweep · retire AAMC vocab from code surface#69
hizrianraz merged 1 commit into
mainfrom
chore/ain-243-purge-sweep-api-v2

Conversation

@hizrianraz
Copy link
Copy Markdown
Contributor

Summary

Final piece of the cross-repo AIN-243 sweep, paired with sdk #11 + #12, mcp-server #12, ainfera-os #49, routing #2. Retires AAMC / TrustScore / Voter / Council vocabulary from the api code surface.

Changes (9 files, +32 / -213)

  • adapters/openai.py + adapters/upstream_aliases.py — comment reframes ("AAMC voter pool" → "canonical routing backends").
  • orm.py — comment cleanup on the catalog-eligibility flag.
  • routers/stats.py — leaderboard endpoint comment reframe.
  • services/response_normalizer.py + services/routing.py — comment cleanup.
  • scripts/seed_dev.py — display names: e.g. "GPT-5.5 Pro (AAMC voter)""GPT-5.5 Pro".
  • tests/integration/test_aamc_invariants.py → renamed to test_routing_backends_invariants.py. Test logic unchanged — still enforces the canonical 5-backend lock (Opus, GPT-5.5, Gemini, Grok, Mistral-Large).

No runtime behavior change. Pure vocabulary cleanup.

Why

Per Ontology v1.2 amendment (2026-05-22): ATS/AAMC retired as standalone methodologies; their value folded into Routing (q_empirical for trust signal; M_allowed for eligibility veto). Ontology v1.3 (2026-05-23) further made Mithril the canonical product the doctrine leads with.

Verify

  • CI green (lint, mypy, pytest — pytest -x -q tests/unit tests/smoke passed locally: 483 passed).
  • grep -rni "aamc voter\|voter pool\|TrustScore\|\\bCouncil\\b" ainfera_api/ returns empty (modulo intentional historical references in docs/comments).
  • The renamed test_routing_backends_invariants.py runs identically to the prior test_aamc_invariants.py.

Provenance

Founder-authored work that was sitting in git stash (parked during PR #67's rebase to avoid intermingling with the Mithril keystone). Popped + committed as part of the "go deliver end to end and push" sweep on 2026-05-23.

🤖 Generated with Claude Code

Final piece of the cross-repo AAMC retirement (paired with sdk #11+#12,
mcp-server #12, ainfera-os #49, routing #2). Removes references to
"AAMC voter" / "voter pool" / "Council" in code comments + display
names + the (now-defunct) invariant test file.

Changes:

- adapters/openai.py: comment reframe — "AAMC voter pool" →
  "canonical routing backends".
- adapters/upstream_aliases.py: same.
- orm.py: drop the `aamc_voter` flag field-comment reference (the
  field itself stays — was repurposed as a generic catalog-eligibility
  flag; just rename the rationale in the comment).
- routers/stats.py: leaderboard endpoint comment reframe.
- services/response_normalizer.py: comment cleanup.
- services/routing.py: comment cleanup.
- scripts/seed_dev.py: display names reframed
  ("GPT-5.5 Pro (AAMC voter)" → "GPT-5.5 Pro").
- tests/integration/test_aamc_invariants.py → renamed to
  test_routing_backends_invariants.py. Test logic unchanged — it
  enforces the canonical 5-backend lock (Opus, GPT-5.5, Gemini, Grok,
  Mistral-Large), reframed away from the retired AAMC framing.

No runtime behavior change. Pure vocabulary cleanup.

Per Ontology v1.2 amendment (2026-05-22) which retired ATS/AAMC and
folded their semantics into Routing (`q_empirical` for trust;
`M_allowed` for eligibility veto). Ontology v1.3 (2026-05-23) further
made Mithril the canonical product the doctrine leads with.

Co-Authored-By: Claude <noreply@anthropic.com>
@linear-code
Copy link
Copy Markdown

linear-code Bot commented May 23, 2026

AIN-243 [Cleanup] Retire ATS/AAMC from code + public site — specs, SDK, MCP, CLI, API, marketing (Notion canon already done)

ATS and AAMC were RETIRED as methodologies 2026-05-22 (founder decision — focus on Routing + Ontology only, post "Inference for AI Agents" pivot). The Notion canon is updated, but ATS/AAMC are still wired through LIVE CODE + the public website. This ticket tracks the code/product cleanup so a future Claude Code session does it deliberately — NOT a silent find-replace, because some of it is shipped product that currently sells these.

Why this matters

A future Claude Code session reading the repos (not just Notion) will see ATS/AAMC as live and may extend them. The retirement isn't real until the code + public surfaces reflect it.

Footprint found (2026-05-22 scan)

Public website (ainfera-ai/web) — PRODUCT DECISION, do first:

Specs repo (ainfera-ai/specs):

  • ats/spec.md + ats/CHANGELOG.md (v1.0)
  • aamc/spec.md + aamc/CHANGELOG.md (v1.1)
  • _meta/alignment.md (ATS↔NIST), _meta/spec-urls.json
  • → Mark specs DEPRECATED/retired (keep as historical or remove from public spec index)

SDK (ainfera-ai/sdk / ainfera_sdk):

  • trust.py (TrustScore.recompute/evaluate)
  • → Deprecate trust module

MCP server (ainfera-ai/mcp-server):

  • ainfera_mcp/tools/trust_score.py (get_trust_score tool)
  • → Remove/deprecate the trust_score MCP tool

CLI (ainfera-ai/...):

  • commands/trust_check.py, actions/trust-check/ (GitHub Action), actions/README trust-check
  • → Deprecate trust-check command + action

API (ainfera-ai/api):

agents/tulkas/runner.py:

  • compliance_veto_test "probe each AAMC voter" → reframe as routing compliance-veto (M_allowed), not AAMC

What is NOT in scope (leave alone)

  • Historical/closed Linear tickets (AIN-24, 107, 109, 141, 150, 206, etc.) — accurate records of what shipped; do not rewrite history.
  • The compliance-veto CONCEPT survives in Routing as M_allowed (eligibility gate). Don't delete it — reframe it.
  • The 5 frontier models survive as routing backends/catalog. Only the council/voter/governance framing dies.

Acceptance criteria

  • Public site: AAMC/ATS narrative replaced or removed (founder/Varda GTM decision first)
  • specs: ats + aamc marked deprecated/retired; removed from public spec index
  • SDK trust.py deprecated
  • MCP trust_score tool removed/deprecated
  • CLI trust-check command + GitHub Action deprecated
  • API: AAMC voter/governance framing reframed; model adapters retained as routing backends
  • tulkas runner: compliance_veto_test reframed to Routing M_allowed
  • grep sweep: no repo presents ATS/AAMC as a LIVE methodology (historical mentions OK if marked)

References

Notion canon updated 2026-05-22: ATS page + AAMC page SUPERSEDED-headed; old "🧬 27 Ontology v1.0" + "L2 Routing" + "Varda Manual" banner-guarded; Ontology v1.2 + Delivery Index are live canon.

Review in Linear

@hizrianraz hizrianraz merged commit 3852dd9 into main May 23, 2026
4 checks passed
@hizrianraz hizrianraz deleted the chore/ain-243-purge-sweep-api-v2 branch May 23, 2026 12:06
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