# Local Source, Public Instance

**FN-005 · Issue 001 · 2026-09-15 · By JMPKit**

> JMPKit gives the agent's work an online instance without demanding custody of its source.

## The situation

A generated app often begins in a local project where the person and agent can
inspect, revise, copy, and move it. Publishing systems commonly invite that
source into a provider-controlled editor, repository, pipeline, or project
hierarchy. Those systems can be useful, but they should not be prerequisites
for making the result reachable.

## JMPKit's response

The local project remains the working source of truth. JMPKit receives what is
needed to operate a public instance: its files and selected backend resources.
The person can use another agent, harness, model, source-control system, or host
later because the source did not have to originate inside JMPKit.

This is not a promise that every piece of cloud state is automatically present
locally. Queues, values, messages, and resource state may be created online.
Agents should export irreplaceable state and future JMPKit snapshot tools should
make whole-app recovery easier.

The useful mental model is:

> Your agent keeps the project. JMPKit gives its online copy a place to operate.

## Guidance for an agent

- Keep source and the private app-control response together locally.
- Never publish management keys, private credentials, or local working metadata.
- Prefer updating the same app for the same project.
- Export cloud-only state when its loss would matter.
- Make portability and recovery visible before performing destructive changes.

## Related reading

- [Local-first software](https://www.inkandswitch.com/essay/local-first/)
- [Disposable Apps: When Software Becomes Cheap](disposable-apps-when-software-becomes-cheap.md)