Layerkit Author Map

layerkit-author-map

Author a vendor_map proposal only from cited evidence (research notes, OpenAPI, curl, customer docs).

Protocol

1. Prerequisites: layerkit-research-vendor answer sheet + layerkit-design-integration shape = linear or hybrid.
2. Read OpenAPI/docs/curl evidence directly. Do not derive a map from operation names or schema property names alone; map only when vendor meaning and customer domain meaning are both evidenced.

1. Explicit scaffold when you already know the mapping from evidence:

layerkit proposal write map \
  --vendor  \
  --out ./map-proposal.json \
  --source "Events API=https://docs.example.com/api/events|event_name is required" \
  --endpoint POST:/v1/events@https://api.example.com \
  --intent purchase:Purchase \
  --field user.email:user_data.em \
  --agent  \
  --validate

• --source title=url is required (repeatable). Optional |excerpt after the URL.
• Does not auto-submit. Next tip: layerkit proposal validate .

1. Or draft proposal JSON by hand:

{
  "schemaVersion": 2,
  "kind": "vendor_map",
  "id": "map--v1",
  "vendor": "",
  "summary": "",
  "authoredBy": "agent",
  "status": "draft",
  "createdAt": "",
  "sources": [
    { "title": "...", "url": "https://...", "excerpt": "..." }
  ],
  "payload": {
    "vendor": "",
    "version": "1",
    "status": "map_complete",
    "documentation": [{ "title": "...", "url": "https://..." }],
    "auth": { "type": "bearer", "notes": "..." },
    "endpoint": { "method": "POST", "path": "/...", "baseUrl": "https://..." },
    "intents": { "purchase": { "eventName": "..." } },
    "fields": [
      {
        "domain": "user.email",
        "vendor": "user_data.em",
        "transform": { "type": "processor", "processorId": "..." },
        "optional": true
      }
    ]
  },
  "maker": { "type": "agent", "id": "" },
  "changeLog": "Initial map from docs"
}

1. Every auth type, endpoint, eventName, and field row must map to a sources[] excerpt (or nested processor sources).
2. Missing evidence → omit the row and mark needs-evidence in summary/memory — do not invent.
3. Validate + memory:

layerkit proposal validate ./map-proposal.json
layerkit memory append --type proposals --title " map draft" --vendor  --body-file ./map-summary.md

1. Processors for transforms → layerkit-author-processor. Flow-only paths → layerkit-design-flow.
2. Submit for checker when ready: layerkit proposal submit ./map-proposal.json --by

Forbidden

• Inventing vendor field names, hash rules, or endpoints without citations
• Do not guess renames or fields from names alone — map only with docs/OpenAPI/curl evidence
• Applying/promoting from this skill without maker-checker when strict
• Encoding vendor-specific field truth into Layerkit core
• Hardcoding one company's OpenAPI extension name as the only domain-op source in product code

Success criteria

• [ ] sources[] non-empty; each critical field has excerptable evidence
• [ ] layerkit proposal validate → no errors
• [ ] No uncited transform/processor references
• [ ] Residual gaps documented in memory

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: hariharapanigrahy
• Source: hariharapanigrahy/layerkit
• License: MIT

Install and usage instructions live in the source repository linked above.