v0.1.0 Draft — Open Standard

Stop Prompting.

Start Specifying.

The open industry standard that transforms random AI prompting and unpredictable code generation into structured, precise, and universally acceptable software specifications.

Try MyAgenticPlatform → ⭐ Star on GitHub
rules.spec.yaml — MAP Spec v1.0.0
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()"

AI guesses.
MAP Spec doesn't.

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

"Build me a todo app with user auth and offline support"
🎲 AI picks MySQL (you wanted PostgreSQL)
🎲 AI uses MD5 for passwords (critical bug)
🎲 AI hard-deletes user data (compliance violation)
🎲 AI invents 3 tables you didn't ask for
🎲 Offline sync logic is wrong
🎲 Every run produces different output

✓ With MAP Spec

RULE-001: bcrypt cost=12, never log passwords [critical]
RULE-004: Soft delete only, deleted_at timestamp [critical]
data.spec.yaml: 3 exact tables, typed columns, indexes
api.spec.yaml: 8 endpoints with exact request/response
AI uses exactly what you specified
Security rules enforced — no exceptions
Data integrity guaranteed by spec
Zero invented tables or endpoints
Offline sync matches business rules
Reproducible output every time

7 layers.
Zero ambiguity.

Every MAP Spec project contains 7 layers. Together they form a complete, unambiguous contract that AI systems consume to generate accurate, predictable output.

01 🧬

Meta

meta.spec.yaml

Project identity, technology stack declaration, constraints

02 📋

Functional

functional.spec.yaml

Features, user stories, Given/When/Then acceptance criteria

03 🔌

API

api.spec.yaml

Every endpoint, request/response contract, side effects

04 🗄️

Data

data.spec.yaml

Exact database schema, tables, columns, indexes, relations

05 🎨

UI

ui.spec.yaml

Every component, props, state, interactions, routing

06 ⚖️

Rules

rules.spec.yaml

Business logic guardrails AI must never violate

07 🧪

Quality

quality.spec.yaml

Test suites, coverage requirements, performance targets

Brief to spec
in minutes.

MyAgenticPlatform is the reference implementation — the fastest and most accurate MAP Spec generator in existence.

01

Describe your product

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 — Artifacts
02

Generate MAP Specs

7 specialised agents convert your artifacts into a complete MAP Spec package — all 7 layers, YAML format, AI-ready.

Phase 2 — MAP Specs
03

Generate accurate code

AI code generators consume your MAP Spec and produce code that matches exactly what you specified. No drift. No surprises.

Phase 3 — Code

The standard is free.
The generator is best.

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.

🌐

Open Standard

MIT licensed. Read it, implement it, build tools around it. No vendor lock-in. The spec belongs to everyone.

🤖

AI-Optimised

Written so AI models parse with zero ambiguity. Every field serves a purpose. The aiInstruction field is mandatory.

📐

Stack-Aware

Declare your stack in meta.spec.yaml. All 7 layers adapt — no generic advice, no technology drift.

Validatable

Every MAP Spec project can be checked for completeness and consistency before a single line of code is written.

🔄

Versioned

map-spec: "1.0.0" in every file. Specs evolve formally. Full change history. Breaking changes are major versions.

🏗️

Human-Readable

YAML format. Any developer can read and write MAP Spec without tooling. Stakeholders can review and approve.

👨‍💻
👩‍💼
🧑‍🚀
👨‍🎨
Join early builders already following the standard

Get early access to
MyAgenticPlatform

The first MAP Spec generator. Brief in, specs out.
Be first when Phase 3 code generation ships.

✓ You're on the list! We'll be in touch when early access opens.

No spam. Unsubscribe any time.