The operating infrastructure for institutions.

Aura is where an institution runs its public and member-facing life — verified identity, members, spaces, announcements, correspondence, and live sessions, on one accountable record. Operational today, distributed across web and app stores.

Institution operating infrastructure.

Aura is the system an institution runs its public and member-facing life on: verified identity, members, spaces, announcements, correspondence, and live sessions, on one accountable record. Operational today and publicly distributed — Aura Platform LLC and Bajwa Writes operate as verified institutions on it (alongside a small group of early institutional users).

VerifiedDomain-verified institutional identity; only the authorized voice can speak for the institution

AccountableOne record across members, spaces, announcements, and correspondence — anyone can audit what the institution committed to

GovernedGovernance over who speaks for the institution and on whose authority — enforced by the platform

DistributedPublicly distributed on the web, Microsoft Store, and Apple App Store; Android via Google Play closed testing. Full distribution: Availability.

The institutions that must be trusted by the people they serve.

Municipalities, schools and universities, associations, nonprofits, chambers of commerce, professional bodies, religious organizations, and companies. Different mandates, one thing in common: every institution that must be trusted by the people it serves.

  • MunicipalitiesCivic governments and public agencies
  • Schools & universitiesAcademic institutions with members and a public record
  • AssociationsMember organizations and professional bodies
  • NonprofitsMission-aligned organizations accountable to a public
  • Chambers of commerceConvening bodies with members and stakeholders
  • Religious organizationsCongregations and member-facing bodies
  • Regulatory bodiesMandates that require a durable record
  • CompaniesFirms whose public voice must be verifiably theirs

A verified voice, an accountable record, and governance — together, in one place.

Institutions adopt Aura for a verified voice members can trust, an accountable record of what was said and committed, and governance over who speaks for the institution. The urgency is new: as AI makes impersonation of any institution trivial, and members and regulators increasingly expect proof that a message is genuinely official, a scattered, unverified presence becomes a liability.

What the disconnected stack can't supply

The conventional institutional presence is scattered across a website, email, social accounts, chat, PDFs, and portals. None of those surfaces can prove a message is genuinely official, none holds an accountable record across all of them, and none governs who is authorized to speak.

What Aura supplies

Aura is the one place that supplies what the disconnected stack cannot — verified identity, an accountable record, and governance, together. The institution runs its public and member-facing life on a single substrate instead of stitching one together after the fact.

An institution-voice reply tagged RESOLVED with a typed pointer back to the commitment.

Beneath the operating surface, this is how the accountable record holds. When the institution speaks, the platform records what it committed to. When the commitment is met, a later reply is tagged as resolved and carries a typed pointer back to the original commitment. Closure is recorded as a structural relationship — not as an editorial claim.

Three accountability tags

  • COMMITMENTInstitution will act
  • UPDATEIn-flight progress on a prior commitment
  • RESOLVEDClosed; with typed pointer back to the original commitment

Why typed

A commitment that exists as styled text inside a feed decays. Typed pointers make resolution structural. A reader two years later can trace what the institution committed to, what updated, what closed.

Only the institution's authorized voice can carry an accountability tag. Personal users cannot tag commitments on an institution's behalf. The platform enforces this.

Three speech modes. The institution speaks; the user is subscript.

Governance over who speaks is enforced structurally. Institutional speech is typed. A single account can speak as a personal user, as an affiliated member of an institution (disclosed), or as the authorized voice of the institution itself. The mode is per-post, not per-account.

The three modes

  • PersonalNo institutional affiliation
  • Affiliated personalMember of an institution, speaking personally — affiliation disclosed
  • Authorized institutionalAuthorized to speak as the institution's voice

When the mode is authorized institutional, the visual rendering places the institution avatar primary and the user avatar as subscript. The hierarchy of the speech mode is the visible hierarchy. The institution is the speaker; the user is the channel through which the institution spoke at that moment.

This is structural, not stylistic. A regulated-sector communications director rendering an official statement gets institutional weight automatically — and a later reader can verify who authored on whose authority through the public record.

Continuation crosses public space boundaries.

A commitment posted in one public space (City Council Discourse) may be substantively continued months later in another (Transit Planning Discourse). A typed continuation pointer makes the relationship traceable across thread, space, and time.

Cross-thread memory is structural, not metadata. A reader walking the public record from a new post can follow continuation pointers backward to the originating commitment, regardless of which public space the discussion has moved into.

This matters institutionally. Civic accountability frequently crosses contexts — a commitment in a council session is continued in a transit planning session is updated in a public hearing. The platform makes this walkable.

Public space hosts

Each public space is a discourse host with its own name, status, and ordering. Posts opt in to a space; replies inherit the parent's space. The public record crosses spaces explicitly through typed pointers — not implicitly through search or recommendation algorithms.

Read-only public-discourse aggregates, not personalised feeds.

Open commitments compute deterministically. Anyone can audit.

Discourse intelligence is six read-only aggregates of the public record. The most-quoted aggregate — open commitments — is a deterministic computation: total commitments minus distinct resolutions. (Figures below are illustrative sample values that demonstrate the computation, not live production metrics.)

127

Open issues

Unanswered questions across all institutional surfaces.

8

= 12 commitments − 4 resolved

Open commitments

Deterministic computation. Anyone can audit.

34

Spaces active

Public spaces where institution voice has substantively spoken.

42

Awaiting institution voice

Trivial replies filtered before counting.

18h

Avg first-response

Median latency from public question to institutional reply.

7

Co-engaged institutions

Institutions sharing public discourse threads.

Posts connect to posts through typed pointers. The graph is the audit trail.

Aura is a public record, not a feed. Reply pointers create the reply tree. Resolution pointers create resolution edges across the record. Continuation pointers create continuation edges across public spaces. The record is the platform's history rendered as walkable structure.

A reader interested in what a specific institution committed to during a specific year walks the record: filter institutional posts by institution, by date, by accountability tag. For each commitment, follow forward to its resolutions. The result is a substantive answer to a substantive civic question — without aggregation lies, without algorithmic curation, without engagement reranking.

This is the substantive difference from social-network platforms. Social networks rank for engagement; substantive truth and high-engagement content correlate poorly. Aura ranks for nothing — the record is the surface. Discourse intelligence aggregates the record; it does not curate it.

Commitments persist until resolved. UPDATE and RESOLVED are typed, not editorial.

On a social-network feed, a post made today is gone in 72 hours. On a public record, a commitment posted today remains an open commitment until a typed resolution with a pointer back has been authored.

The platform does not decay commitments on a time horizon. A commitment from last year is the same on-record fact as a commitment from this week. The institutional accountability arc is durable in a way feeds aren't.

This is the institutional reason civic governments, public agencies, regulatory bodies, mission-aligned nonprofits, and academic institutions choose this platform over social-network alternatives: the public record serves the civic function their institutional mandate requires. Engagement-driven platforms cannot.

Institution → Aura. Operation → Orchestrate. Continuity → Bajwa Writes.

One ecosystem on a shared substrate. Aura, Orchestrate, and Bajwa Writes share one verified identity, one governance pattern, and one accountable record — an institution verified on Aura is already trust-established if it runs outbound on Orchestrate, and both write to a record Bajwa Writes preserves. Each system makes the others stronger.

Deterministic governors
IdentityVerification SpaceModeration SpeechModeAuthorization
The audit is the platform.

Read the architecture.

The operating infrastructure above is documented openly, down to the structure. Every claim on this page is rendered by the platform itself; the discourse canon documents how it works.

Stand up your verified institution.

Aura is institution operating infrastructure, operational today. Stand up your verified institution on the platform, or reach the founder directly — verified institutions, procurement reviewers, and investors are all welcome.

Institutional & investor hello@auraplatform.org

Architecture canon Aura Platform LLC

Investor narrative Open the deck

Two products, one governance pattern — evidence it generalizes rather than fitting a single domain. The same hand built both: a thirty-year operator turned platform architect.

The founder →