Packages

@paramira/suite-identity

One identity for the Paramira Suite's tabs: abantu and isoko keep theirs in the Suite's local service, the same record iwacu uses, and every tab follows changes.

License: AGPL-3.0-or-later

Source: packages/suite-identity

What it does

One identity across the Paramira Suite's tabs (docs/plans/app-roles.md, Phase 5). The Suite serves abantu, isoko and iwacu from one origin, and iwacu's local service keeps the identity. abantu and isoko, built for the Suite, read and write that record instead of their own copy; creating one happens under a lock all tabs share, and a change in one tab reaches the others. A key behind the WebAuthn lock stays locked through all of it.

AGPL-3.0-or-later.

Used by

Apps: abantu, isoko-web, iwacu-nuxt

Uses

No dependencies.

storage

A minimal async KeyValueStore contract (get/set of string values) plus an in-memory implementation for tests and throwaway node services. No opinion on where any real app actually persists data.

testimony

Anonymous journey testimonies, as inzira defines them: the journey schema (stops, accounts, consent), coarsening per stop role, path-uniqueness checks, sealed submissions signed by a per-testimony key, edits, consent narrowing, withdrawal, two-reviewer publication with an outside reviewer, and a chain-of-custody check anyone can run.