Start Specifying.
The open industry standard that transforms random AI prompting and unpredictable code generation into structured, precise, and universally acceptable software specifications.
map-spec: "1.0.0" layer: "rules" rules: - id: "RULE-001" domain: "security" name: "Password hashing" rule: "All passwords must be hashed before storage" implementation: "bcrypt with cost factor 12" severity: "critical" aiInstruction: "Always call bcrypt.hash(password, 12) before any INSERT to users table. Never log passwords." references: ["US-001", "API-001"] - id: "RULE-002" domain: "data" name: "Soft delete only" rule: "User records must never be hard deleted" severity: "critical" aiInstruction: "Never generate DELETE FROM users. Always use UPDATE users SET deleted_at = NOW()"
The Problem
Give AI a vague prompt and it makes hundreds of micro-decisions — choosing databases, inventing business rules, designing APIs — all without knowing what you actually want.
❌ Without MAP Spec
✓ With MAP Spec
The Standard
Every MAP Spec project contains 7 layers. Together they form a complete, unambiguous contract that AI systems consume to generate accurate, predictable output.
Meta
meta.spec.yamlProject identity, technology stack declaration, constraints
Functional
functional.spec.yamlFeatures, user stories, Given/When/Then acceptance criteria
API
api.spec.yamlEvery endpoint, request/response contract, side effects
Data
data.spec.yamlExact database schema, tables, columns, indexes, relations
UI
ui.spec.yamlEvery component, props, state, interactions, routing
Rules
rules.spec.yamlBusiness logic guardrails AI must never violate
Quality
quality.spec.yamlTest suites, coverage requirements, performance targets
How It Works
MyAgenticPlatform is the reference implementation — the fastest and most accurate MAP Spec generator in existence.
Write a brief in plain English. What you're building, who it's for, what it needs to do. No technical knowledge required.
Phase 1 — Artifacts7 specialised agents convert your artifacts into a complete MAP Spec package — all 7 layers, YAML format, AI-ready.
Phase 2 — MAP SpecsAI code generators consume your MAP Spec and produce code that matches exactly what you specified. No drift. No surprises.
Phase 3 — CodeWhy Open
MAP Spec is MIT licensed. Anyone can read it, implement it, build tools around it. We make money by being the best at generating it.
MIT licensed. Read it, implement it, build tools around it. No vendor lock-in. The spec belongs to everyone.
Written so AI models parse with zero ambiguity. Every field serves a purpose. The aiInstruction field is mandatory.
Declare your stack in meta.spec.yaml. All 7 layers adapt — no generic advice, no technology drift.
Every MAP Spec project can be checked for completeness and consistency before a single line of code is written.
map-spec: "1.0.0" in every file. Specs evolve formally. Full change history. Breaking changes are major versions.
YAML format. Any developer can read and write MAP Spec without tooling. Stakeholders can review and approve.
The first MAP Spec generator. Brief in, specs out.
Be first when Phase 3 code generation ships.
No spam. Unsubscribe any time.