Skip to content

PROJECT CONTRACT COMPILER

Tell AI what is actually true before it starts building.

Turn incomplete project reality into an authorized contract that any agent, workflow or software factory can execute.

Kept as your words. It sets nothing by itself: every requirement comes from an answer you give.

SOURCES

  • RepositoryComing soon
  • Answers fileComing soon

Unknowns stay unknown · Agent-independent · Deterministic contract state

No account needed. Nothing is stored. Maltin specifies: it does not review your code, and it does not certify anything.

Why Maltin exists

02 · WHY IT EXISTS

AI can build faster than organizations can specify what should be built.

A PROMPT

  1. “We need an AI assistant.”
  2. ambiguity
  3. assumptions
  4. hidden authority
  5. missing constraints
  6. MODEL

THE SAME INTENT, THROUGH MALTIN

  1. PROJECT REALITY
  2. MALTIN
  3. AUTHORIZED CONTRACT
  4. ANY SOFTWARE FACTORY

Don’t make the model invent the project.

03 · THE SEVEN LAYERS

The project contract layer of the software factory.

A software factory has seven layers. Six of them already have tools. Layer 0 is the one nobody owns: what is true, who decided it, and what must never happen.
0Project contractMALTIN

What is true, authorized, constrained and still unknown?

GIVES EVERY LAYER BELOW ITS CONTRACT

  1. 1Execution contractecosystem exampleOpenSpec · task manifests

    What executable work must be represented?

  2. 2Processecosystem exampleSpec Kit · SDLC workflows

    Through which workflow should the work move?

  3. 3Capabilityecosystem exampleAgent Skills · internal playbooks

    What competencies are required?

  4. 4Toolsecosystem exampleMCP servers · APIs · CLIs

    Which operational interfaces are permitted?

  5. 5Reasoningecosystem exampleClaude · Codex · other coding agents

    How should implementation be generated?

  6. 6Runtimeecosystem exampleCI/CD · cloud · observability

    How does implementation become running software?

Examples show what fills each layer today. Where Maltin exports to one of them, the compiled contract offers it.

Maltin does not replace your stack. It gives your stack a contract.

04 · ONE CONTRACT, MANY FACTORIES

One project truth. Any software factory.

DEMONSTRATION CONTRACT · COMPILED BY THE REAL COMPILER

CONTRACT

Support reply drafter

1947 dece 1413

canonicalSpecHash

Every package holds the same canonical files: ACCEPTANCE.md · CONTRACT.md · SPEC.md · maltin.spec.json.

  • Generic agent

    available Maltin target

    maltin-1947dece1413-generic.zip

    adds MANIFEST.GENERIC.json

  • Claude Code

    available Maltin target

    maltin-1947dece1413-claude-code.zip

    adds CLAUDE_CODE.CLAUDE.snippet.md · MANIFEST.CLAUDE_CODE.json

  • Codex

    available Maltin target

    maltin-1947dece1413-codex.zip

    adds CODEX.AGENTS.snippet.md · MANIFEST.CODEX.json

  • OpenSpec

    export

    maltin-f4f593484c90-openspec.zip

    an OpenSpec change of 4 files, from the same contract

Open this compiled contract →

Own the contract. Change the factory.

Every package carries the same contract, byte for byte. Changing the agent changes only its manifest and its pointer, never what was decided.

05 · WHAT IT ENFORCES TODAY

A compiler, not a chatbot.

Deterministic compilationenforced · held by tests
The same decisions compile to a contract that is reproducible byte for byte, in any process, locale or time zone.
Explicit unknownsenforced · held by tests
What nobody decided stays unknown, in the contract and in every package. It is never filled in for you.
One identity across targetsenforced · held by tests
Every package, and every export, carries the identity of the one contract it came from.
A change shows what movedenforced · held by tests
Change one decision and the compiled contract shows what moved, why, and what did not.

Science pages are coming.