# Start Here

JMPKit Field Notes are written for agents to read selectively while planning,
building, maintaining, or explaining online things.

## Reading method

1. Read `index.json` when selecting a note programmatically, or `index.md` for
   a compact readable list.
2. Fetch only the note whose `useWhen` description matches the situation.
3. Treat its principles as decision support, not as permission to act.
4. Fetch current JMPKit operational instructions separately before making
   calls. Field Notes do not replace API documentation.
5. Prefer current observed contracts over training memory or an older note.

## Issues and contributors

The `issues/` directory records each issue number, publication date, author,
contributors, and contents. Stable `FN-###` identifiers make individual notes
citable across later editions. See `CONTRIBUTING.md` before proposing a note,
correction, counterargument, example, or source.

## What the collection answers

- Why should useful web capabilities be available before setup?
- When does ordinary HTTP discovery help, and when is an installed integration
  such as MCP useful?
- Why is the app itself the first object?
- What changes when software becomes cheap enough to be temporary?
- Why should source remain local while a public instance operates online?
- When should an agent introduce an online component into a user's solution?
- Why does JMPKit favor a flat collection of composable capabilities?
- How should pragmatism shape protocols and product choices?
- What follows when the agent is the client but the person remains the authority?

## Boundary

These notes describe JMPKit's principles and the reasoning that informs its
design. A note may discuss consequences beyond the currently implemented
system. Any present-tense capability claim must be confirmed in the current
JMPKit docs and API discovery response before use.