For authors

Publish your architecture.

Your code stays on GitHub. The registry stores the manifest and the commit it points to. Four steps, about a minute.

Init

Creates genpm.json from your repo.

genpm init

Write the rules

An AGENTS.md with Purpose, Map, Integration, Conventions and Don't.

AGENTS.md

Tag

Tags are immutable. Branches are rejected.

git tag v1.0.0 && git push --tags

Publish

Verifies the tag, scans the rules, lists the package.

genpm publish

Manifest builder

Build your genpm.json

Validated in your browser with the same rules as the registry.

genpm.json

{
  "$": 1,
  "n": "@acme/payments",
  "v": "1.0.0",
  "s": {
    "en": "Stripe Checkout and webhooks for Hono"
  },
  "d": "src/lib/payments",
  "l": "MIT",
  "k": [
    "billing",
    "stripe"
  ],
  "g": {
    "@core/db": "^1.0.0"
  },
  "p": {
    "stripe": "^17.0.0"
  },
  "e": [
    "STRIPE_SECRET_KEY"
  ]
}

✔ valid · schema v1

Before you publish

Quality checklist

A LICENSE file that matches l.
AGENTS.md under 16 KB, with the five recommended sections.
No secrets, no .env files, no build output in the injected tree.
Tests excluded with .genpmignore.
A summary your users understand in one line.