StateMirror Developer Plugin

The Developer Plugin is an integration assistant. It helps a developer interpret StateMirror's verified interfaces and apply them to an application decision path.

DEVELOPER
    |
    v
STATEMIRROR PLUGIN
    |
    v
APPLICATION INTEGRATION
    |
    v
STATEMIRROR CORE

A useful StateMirror integration preserves the facts that mattered to an application decision after that decision is known and before the resulting application action executes.

For example, assume authentication middleware has already validated a JWT and the application uses the following authorization logic.

const allowed = claims.role === "reviewer";

if (!allowed) {
  return reply.code(403).send({ error: "forbidden" });
}

return readReport();

READ STATE
    |
    v
MAKE DECISION
    |
    v
CAPTURE EVIDENCE  <-- StateMirror
    |
    v
EXECUTE ACTION

The application still decides what happens if evidence capture fails or times out. StateMirror does not make the application action and evidence submission atomic.

The plugin is deliberately narrow. Its useful work happens where application code meets StateMirror Core.

AI assistance does not expand StateMirror's authority or its integrity claims.

• The plugin does not authorize access or determine whether a decision is correct.
• It does not make application decisions or execute application actions.
• It does not replace StateMirror Core or become the evidence system of record.
• It does not prove that submitted upstream facts were true or fresh.
• It does not turn integrity verification into proof of policy correctness, compliance or legal non-repudiation.
• It should not preserve raw credentials, bearer tokens or direct credential derivatives as decision evidence.
• It does not invent the application's capture-failure, retry, transaction or recovery policy.

1. Run StateMirror Core locally. Start PostgreSQL and Core using the published Quickstart.
2. Choose one application decision. Show the plugin the state reads, decision logic and resulting application action.
3. Identify the decision boundary. Determine where the application knows its decision but has not yet executed the action.
4. Define the smallest useful evidence. Preserve decision-relevant facts and useful references without copying the entire request context.
5. Review failure ownership. Decide what the application does if capture fails, times out or returns an uncertain result.
6. Test against Core. Use synthetic nonsecret evidence, submit it to the authorized local instance, retrieve the snapshot and verify its integrity.

A passing integration test establishes that the tested application path can submit and retrieve evidence under that configuration. It does not prove every production decision will be captured or that the recorded facts were externally correct.

StateMirror Core remains the implementation and evidence contract. The Developer Plugin helps apply that contract to application code.

Start with a local Core instance, one decision path and synthetic evidence. Keep production credentials and customer evidence out of exploratory plugin conversations unless your organization has separately approved that handling.