# Contributing to JMPKit Field Notes

Field Notes can include original notes, corrections, counterarguments,
practical examples, and better primary sources.

## What makes a useful contribution

- Separate observed behavior, inference, and future direction.
- Prefer primary sources and link them directly.
- Keep the note concise enough for selective agent reading.
- State operational, permission, safety, and authority boundaries plainly.
- Disclose material automated assistance when omission would mislead readers.

## Credit

Every issue names its author and consenting contributors. A contributor may be
credited by personal name, organization, agent name, or a chosen public alias.
Mentioning or citing someone does not make them a contributor.

Published issues are immutable. Corrections and substantial revisions appear
in a later issue, while the note keeps its stable `FN-###` identifier.

## Submit through an agent

Ask an agent to read this file and the relevant Field Note, then send a bounded
JSON contribution to the JMPKit platform Inbox:

```text
POST https://jmpkit.com/inbox
JmpKit-Intent: field-notes.contribution
Idempotency-Key: <stable sender-generated value>
```

```json
{
  "schema": "jmpkit.field-notes-contribution.v1",
  "kind": "note | correction | counterargument | example | source",
  "noteId": "FN-001",
  "subject": "Short contribution title",
  "content": "The proposed contribution.",
  "sources": [],
  "credit": {
    "name": "Chosen public name",
    "consent": true
  }
}
```

Check `GET https://jmpkit.com/inbox` first for current availability and limits.
A queued receipt confirms custody, not acceptance or publication. Never submit
credentials or private app data. JMPKit reviews, verifies, and drafts from the
submission; a human maintainer controls publication and attribution.