Technical reference

Services

The services that carry Paramira's data: relays, the directory, and the optional ones a community runs.

abantu-rooms

No description yet.

Source: services/abantu-rooms · deployed with Dockerfile, docker-compose.yml

Packages it uses: none from the monorepo

directory

paramira protocol directory — catalog, signed adoption, agreements, community roles, proposal requests. The single authority every app (isoko, abantu, iwacu) reads and writes protocol state through.

Source: services/directory · deployed with Dockerfile, docker-compose.yml

Packages it uses: agreements, auth-sdk, directory-listings, geo, geo-claims, identity, inquiry-board, link-room, protocol-catalog, protocol-core, requirements, signed-request

isoko-market

Isoko DIDComm relay — store-and-forward + WebSocket push, no Firebase

Source: services/isoko-market · deployed with Dockerfile, docker-compose.yml

Packages it uses: none from the monorepo

iwacu-rooms

No description yet.

Source: services/iwacu-rooms · deployed with Dockerfile, docker-compose.yml

Packages it uses: none from the monorepo

relay-auth

No description yet.

Source: services/relay-auth

Packages it uses: none from the monorepo

relay-blobs

No description yet.

Source: services/relay-blobs

Packages it uses: none from the monorepo

relay-push

No description yet.

Source: services/relay-push

Packages it uses: none from the monorepo

testimony-qa

Inzira's optional Ask service (docs/plans/inzira.md, Part 4c). A community runs it so its members can ask questions of what the community published. The static apps can't hold a model's API key, so this holds it.

Source: services/testimony-qa · deployed with Dockerfile

Packages it uses: testimony-qa