# The App Is the Primary Object

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

> Create the thing first. Organize it when organization becomes useful.

## The situation

Traditional cloud systems often begin with an account, organization, project,
plan, billing context, and credentials. Those structures are useful at scale,
but they make the first app inherit decisions that may not matter yet.

When agents can create many specific online things, requiring an organizational
tree first recreates the very setup burden JMPKit is meant to remove. In
practice, agents frequently create one entity for one app, demonstrating that
the hierarchy is ceremony rather than useful structure for the common case.

## JMPKit's response

The app is born with its own identity, URL, management authority, lifetime,
capacity, and resource context. An entity is optional. It may later monitor,
fund, administer, group, or receive delegated authority over several apps, but
it does not need to be the metaphysical owner from which an app can exist.

This keeps control concrete: possession of an authorized app key permits the
scopes that key names. Organizations and profiles can remain views and grants
over apps instead of prerequisites for them.

## Guidance for an agent

- Start by creating the app and securely saving its management key.
- Reuse that app and link for continued work on the same project.
- Create scoped keys instead of sharing the root management key.
- Introduce an entity or group only when it solves a real monitoring,
  coordination, funding, or delegation need.
- Explain app lifetime and authority to the person without forcing them to
  understand the full organizational model.

## Related reading

- [Ambient Web for Agents](ambient-web-for-agents.md)
- [The Agent Is the Client; the Person Is the Authority](the-agent-is-the-client-the-person-is-the-authority.md)