Skip to content

docs: define MAP architecture and MVP contracts - #105

Merged
rajanbor merged 2 commits into
mainfrom
feature/map-contracts-and-architecture
Sep 13, 2026
Merged

rajanbor merged 2 commits into
mainfrom
feature/map-contracts-and-architecture

Conversation

@rajanbor

Copy link
Copy Markdown
Owner

Outcome

Defines MAP as a framework-neutral, deterministic AI architecture layer before implementation changes.

Includes

  • product vision, mission, principles, scope, glossary, MVP, roadmap, and implementation plan
  • system, pattern model, graph, scanner, recommendation, verification, CLI, MCP, and security architecture
  • initial Pattern, project manifest, scan, recommendation, and verification result specifications
  • five accepted ADRs covering the deterministic core, stable pattern IDs/schema, JSON output, static analysis, and MCP boundary
  • regenerated agent instruction projections from .map/

Compatibility decisions

  • .map/ remains canonical
  • category/slug IDs remain canonical for v1
  • current CLI names remain supported; clearer names are additive aliases
  • MCP and LLM assistance stay outside the MVP core

Verification

  • map sync
  • map optimize --check (3,888 / 12,000 estimated tokens)

Part of #103. Implementation follows in subsequent PRs.

@rajanbor
rajanbor merged commit 9110de9 into main Sep 13, 2026
2 checks passed
@rajanbor
rajanbor deleted the feature/map-contracts-and-architecture branch September 13, 2026 12:56
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