Skip to content
Merulan

Acme Ops setup

What an operator supplies to connect the Acme Ops Source, and the verification the provider requires.

Connecting Acme Ops accepts a provider API key the operator pastes once. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

Acme Ops refuses the connection until every item holds.

  • A local or test environment. Acme Ops is the conformance fixture that keeps the provider composition seam honest, and no production workspace connects it.
  • An Acme Ops tenant key issued by the fixture.

Credentials

Acme Ops stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • An API key for the tenant connection, and an agent seat key for the agent role.

Scopes

Acme Ops requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • work-items:read
  • work-items:write
  • agent-seat:act

The tenant connection carries the work-item scopes, and the agent seat carries the act scope.

Verification

Example Source, never verified governs the Acme Ops connection. No provider admits Acme Ops, because no provider exists behind it.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.