Skip to content

ROADMAP.md

Latest commit

 

History

History
290 lines (176 loc) · 13.3 KB

ROADMAP.md

File metadata and controls

290 lines (176 loc) · 13.3 KB
Raw

Roadmap

0.1.0

  • Publish initial profile levels.
  • Publish JSON schema.
  • Publish validator script.
  • Include four flagship examples.
  • Include 16-repo portfolio testbed map.

0.2.0

  • Add boundary model template.
  • Add scoring guidance.
  • Add issue templates for evidence submissions.
  • Add examples from external repositories if maintainers opt in.

0.3.0

  • Add compatibility policy.
  • Add adoption registry.
  • Add CI badge and release notes.

0.4.0

  • Add external review guide.
  • Add AAIF proposal readiness self-audit.
  • Add focused external review issue template.
  • Seek technical feedback in AAIF/LF-style public forums.

0.5.0

  • Add public ecosystem contribution ledger.
  • Track upstream maintainer feedback and recognition gates without over-claiming accepted contribution.

0.5.1

  • Add maintainer review kit for AGENTS.md, MCP, A2A, agent gateway, enterprise, and OSS maintainer review lanes.
  • Make external review and adoption trial paths easier to use without implying endorsement.

0.5.2

  • Update GitHub Actions validation runtime from Node 20 to Node 24 after the hosted runner deprecation warning.

0.5.3

  • Update validation workflow actions to current majors after confirming the hosted-runner warning came from action runtime versions.

0.5.4

  • Record the direct AAIF Observability Working Group onboarding PR in the ecosystem contribution ledger.

0.5.5

  • Record the AAIF Observability Working Group liaison tracker PR in the ecosystem contribution ledger.

0.5.6

  • Record the AAIF Taxonomy & Landscape term style guide PR in the ecosystem contribution ledger.

0.5.7

  • Record the AAIF Taxonomy & Landscape AI usage guide PR in the ecosystem contribution ledger.

0.5.8

  • Add AAIF portfolio recognition roadmap for the 16-repository testbed.

0.5.9

  • Add maintainer growth policy, release checklist, and dependency-license inventory for proposal-readiness hardening.

0.5.10

  • Add adoption trial protocol and issue template for low-friction external review before registry listing.

0.5.11

  • Add twelve month milestone plan and spec change process for public proposal-readiness review.

0.5.12

  • Add security posture plan for reporting, secret safety, supply-chain hygiene, OpenSSF-style future checks, release gates, issue hygiene, and AI-assisted contribution boundaries.

0.5.13

  • Add GitHub Pages-ready docs portal for profile discovery, reviewer entry points, SEO metadata, sitemap, and public review links.

0.5.14

  • Add community engagement plan for AAIF/LF-style forum participation, GitHub review issues, adoption-trial outreach, human-reviewed posting, response cadence, and anti-endorsement boundaries.

0.5.15

  • Add external reviewer program and reviewer-interest issue template for opt-in AGENTS.md, MCP, agent gateway, security, enterprise, and OSS maintainer review lanes.

0.5.16

  • Add second-wave portfolio readiness examples for VoiceGrid Operations, Meeting Intelligence Hub, TenantCommerce Control, and LedgerOps Intelligence.

0.5.17

  • Promote the four second-wave examples to repo-local boundary evidence after publishing product-level docs/AGENTIC_BOUNDARY_MODEL.md documents and closing the matching public readiness issues.

0.5.18

  • Add a single public review packet for AAIF/LF-adjacent forum asks, reviewer routing, current evidence, anti-claims, and copy-ready technical feedback text.

0.5.19

  • Promote the remaining eight portfolio repositories to repo-local boundary evidence.
  • Expand the central profile examples from eight to all 16 enterprise product repositories.
  • Close the matching public readiness issues for AppForge Studio, BrandOps Studio, IdentityCore Platform, KnowledgeStream Hub, CollabBoard Command, LiveOps Broadcast, SkillForge Learning, and WorkGrid Portfolio.

0.5.20

  • Add reviewer quickstart for the 16-repository testbed.
  • Give external reviewers a 20-minute lane-based review path with a copy-ready feedback shape.

0.5.21

  • Add contribution monitoring protocol for upstream PR state, recognition gates, human-only gates, no-noise maintainer rules, and ledger update discipline.
  • Make open contribution work easier to inspect without claiming accepted contribution before maintainer merge or adoption.

0.5.22

  • Add review signal matrix so external reviewers can provide one-comment signals such as useful, too heavy, no fit, or route to AGENTS.md/MCP/A2A/agent gateway.
  • Make public feedback easier to classify into accepted change, follow-up issue, non-goal, compatibility note, or adoption-trial note.

0.5.23

  • Record the AAIF Taxonomy & Landscape Security & Privacy candidate-term contribution posted to issue 18.
  • Preserve the issue 12 no-PR boundary by tracking the comment as editor-triage evidence, not accepted taxonomy content.

0.5.24

  • Record the AAIF Taxonomy & Landscape Workflows & Process Integration candidate-term contribution posted to issue 19.
  • Continue the no-PR candidate-term pattern from issue 12 by treating the comment as editor-triage evidence, not accepted taxonomy content.

0.5.25

  • Record the AAIF Taxonomy & Landscape Accuracy & Reliability candidate-term contribution posted to issue 13.
  • Continue the issue-backed, no-PR candidate-term pattern for AAIF taxonomy editor triage.

0.5.26

  • Record the AAIF Taxonomy & Landscape Agentic Commerce candidate-term contribution posted to issue 14.
  • Continue the issue-backed, no-PR candidate-term pattern for AAIF taxonomy editor triage.

0.5.27

  • Record the AAIF Taxonomy & Landscape Observability & Traceability candidate-term contribution posted to issue 15.
  • Continue the issue-backed, no-PR candidate-term pattern for AAIF taxonomy editor triage.

0.5.28

  • Record the AAIF Taxonomy & Landscape Governance, Risk & Regulatory Alignment candidate-term contribution posted to issue 17.
  • Continue the issue-backed, no-PR candidate-term pattern for AAIF taxonomy editor triage.

0.5.29

  • Record the AAIF Observability & Traceability Working Group trace-model recommendation planning PR opened for issue 12.
  • Track the PR as maintainer-review evidence, not accepted working-group output.

0.5.30

  • Record the AAIF Taxonomy & Landscape Identity & Trust candidate-term contribution posted to issue 16.
  • Continue the issue-backed, no-PR candidate-term pattern for AAIF taxonomy editor triage.

0.5.31

  • Add an AAIF project proposal preflight dossier mapped to the public AAIF proposal form and lifecycle criteria.
  • Keep the formal proposal boundary explicit: public review ready, proposal preflight ready, but not AAIF Growth-stage or Impact-stage proposal ready.

0.5.32

  • Add an external review and adoption operating queue that maps proposal-preflight gaps to reviewer lanes, trial lanes, public proof requirements, and escalation rules.
  • Update public review/adoption surfaces from static artifacts toward concrete external proof-gathering steps.

0.5.33

  • Add AAIF engagement dossier that maps the current AAIF project surface, proposal route, reviewer lanes, proposal boundaries, and 30-day human engagement plan.
  • Make the route to AGENTS.md, MCP/tool readiness, agentgateway governance, Goose/developer workflow, working groups, and future project proposal discussion explicit without claiming endorsement.

0.5.34

  • Add route-signal issue template so external reviewers can leave one structured signal about AGENTS.md, MCP/tool readiness, agentgateway governance, Goose/developer workflow, independent profile fit, or no-fit status.
  • Link the route-signal path from README, the review signal matrix, AAIF engagement dossier, and docs portal.

0.5.35

  • Add route-signal triage labels for route-signal, agentgateway, goose, route-independent, signal-too-heavy, and signal-no-fit.
  • Update route-signal template and review docs so incoming external signals can be classified without turning technical feedback into endorsement or adoption claims.

0.5.36

  • Pin and surface the good-first-review issue so outside reviewers have one visible first action.
  • Link issue #7 from README, public review packet, and docs portal.

0.5.37

  • Add route signal response protocol for recorded signals, accepted changes, follow-up issues, non-goals, route changes, and adoption trials.
  • Link the protocol from README, public review packet, review signal matrix, and docs portal.

0.5.38

  • Add route signal ledger so public reviewer signals and response states have an inspectable queue.
  • Keep the ledger honest by recording that no external route signals have arrived yet.

0.5.39

  • Add reviewer acknowledgement policy for consent-based reviewer credit without implying endorsement, adoption, foundation status, or employer approval.
  • Link the policy from README, public review packet, external reviewer program, route signal ledger, and docs portal.

0.5.40

  • Refresh the route-signal issue template with first-review context links, A2A/interoperability routing, one-sentence response shape, anti-claim checks, and public acknowledgement consent.
  • Update the public review packet release link so outside reviewers land on the current release surface.

0.5.41

  • Refresh the public routing discussion so it points to the current release, pinned review issue, route-signal template, A2A/interoperability routing, and anti-endorsement boundary.
  • Link the public discussion from README, public review packet, and docs portal as the broader technical-feedback path beside the one-signal issue.

0.5.42

  • Refresh the adoption-trial intake path so issue #5, the public review packet, adoption protocol, operating queue, and docs portal point reviewers to the current release.
  • Keep adoption language opt-in only: a trial is not adoption, endorsement, certification, AAIF status, or Linux Foundation status.

0.5.43

  • Refresh the external reviewer call so issue #6, the external reviewer program, external review guide, public review packet, README, and docs portal point reviewers to the current release.
  • Keep reviewer feedback scoped to technical critique and route guidance, not endorsement, adoption, certification, AAIF status, or Linux Foundation status.

0.5.44

  • Refresh the focused AAIF proposal-readiness review path so issue #4, the preflight dossier, proposal self-audit, engagement dossier, public review packet, README, and docs portal point reviewers to the current release.
  • Keep the formal proposal boundary explicit: public review ready and proposal-preflight ready, but not AAIF Growth-stage, Impact-stage, or working-group proposal ready.

0.5.45

  • Add the AAIF forum posting packet for one concise, human-reviewed, non-promotional public ask.
  • Link the packet from README, public review packet, AAIF engagement dossier, and the docs portal.
  • Keep the forum route separate from formal AAIF project proposal submission until external adoption, diverse maintainers, accepted upstream work, and routing feedback exist.

0.5.46

  • Add the AAIF ambassador contribution plan for monthly project-based educational contributions tied to AGENTS.md, MCP, Goose, and agentgateway.
  • Link the plan from README, public review packet, AAIF engagement dossier, community engagement plan, and docs portal.
  • Keep ambassador acceptance, AAIF endorsement, and Linux Foundation endorsement out of scope until public AAIF evidence exists.

0.5.47

  • Add the AGENTS.md enterprise evidence checklist as the first monthly ambassador-style educational contribution.
  • Give maintainers a 20-minute path, copy-ready AGENTS.md starter block, tool-boundary model, human approval gates, OSS fallback notes, and reviewer ask.
  • Link the checklist from README, public review packet, AAIF engagement dossier, AAIF ambassador contribution plan, community engagement plan, forum posting packet, and docs portal.

0.5.48

  • Add the MCP tool boundary evidence checklist as the second monthly ambassador-style educational contribution.
  • Ground the checklist in current MCP tool, schema, annotation, authorization, and security concepts without claiming MCP compliance.
  • Give maintainers a 20-minute path, tool side-effect matrix, annotation mapping, authorization checklist, approval gates, audit evidence, fallback notes, and reviewer ask.

0.5.49

  • Add an MCP review posting packet for one concise, human-reviewed, field-level public ask.
  • Keep the MCP route non-promotional: no auto-posting, no compliance claim, no cross-posting, and no endorsement request.
  • Link the packet from README, public review packet, engagement dossier, ambassador plan, community engagement plan, forum posting packet, and docs portal.

0.6.0

  • Ship the zero-dependency aerp CLI for scanning any local repository.
  • Ship a reusable GitHub Action with JSON and Markdown evidence reports.
  • Add automated evidence gates for Levels 0-3 and keep Level 4 human-reviewed.
  • Add scanner tests, self-scan CI proof, package dry-run proof, and a scanner threat model.
  • Refocus the public site and README on executable adoption instead of document volume.

0.7.0

  • Run the scanner against external repositories only with maintainer consent or read-only public review.
  • Convert real false-positive and false-negative feedback into rule fixtures.
  • Add first external adoption evidence only after a maintainer publicly confirms use.

1.0.0 Candidate

  • Multiple maintainers or public reviewer group.
  • External examples.
  • Stable schema.
  • Public adoption evidence.
  • Clear positioning relative to AGENTS.md, MCP, and agent gateway governance needs.