Circlworld
← Back to Charter Hall

v1.0 · Effective · Charter Hall

Pulse Architecture and Data Use Policy

Charter Hall Document — Circlworld Platform Version: 1.0 Effective: [Phase 1 launch date] Next scheduled review: [Phase 1 launch + 12 months] Owner: Circlworld Platform Team

Plain-language summary

The Pulse is the platform's heartbeat — it captures every meaningful event that happens on Circlworld and streams it to relevant members in real time. Someone joins a circle, you might see it. Someone in your tradition celebrates a milestone, you might see it. Someone in your circle records a contribution, you definitely see it.

But: not every event reaches every member. The Pulse respects privacy boundaries strictly. Your DMs are never in the Pulse. Your Care Concierge conversations are never in the Pulse. Your private profile activity is never in the Pulse.

What is in the Pulse: events you and your fellow members choose to share, organised so the right people see them at the right time.

This document explains exactly what events the Pulse captures, who sees them, and what data is retained.

1. What the Pulse is

The Pulse is a real-time event bus that:

2. The event taxonomy (Phase 1)

The Pulse captures approximately 40 event types organised into 13 categories:

Circle events

Credibility events

Goal events

TEP events (Phase 2)

MRR events (Phase 2)

Storefront events

University events

Outlet events

Plaza events

Town Hall events

Wellbeing events (strict privacy)

Platform events

3. Visibility scopes — who sees what

Every event has one of five visibility scopes:

| Scope | Meaning | Examples | |---|---|---| | PUBLIC | Visible to anyone on the platform with the relevant lens | PlazaPostPublished (Everyone visibility), AggregateThresholdCrossed | | MEMBER_OPTIN | Visible to others only if the originating member has opted to make their activity public | StandingTierAdvanced, CertificationIssued, GoalReached | | CIRCLE_ONLY | Visible only to members of the originating circle | ContributionRecorded, CycleCompleted | | PARTICIPANTS_ONLY | Visible only to direct participants | EndorsementGiven (visible to giver and recipient), WaveSent | | PRIVATE | Visible only to the originating member's own Pulse view | WellnessCheckCompleted, CareConciergeOpened |

These scopes are enforced centrally by the Pulse subscriber service. They are not overridable per member; they are properties of the event type.

4. What is NEVER in the Pulse

The following data is technically isolated from the Pulse infrastructure:

CI gates verify this isolation. Any code path attempting to emit DM, Care Concierge, or dispute content as a Pulse event will fail static analysis.

5. Personalisation — how the Pulse decides what you see

Your personalised Pulse stream is weighted by multiple signals:

| Signal | Default weight | |---|---| | Events from your own circles | Highest (always shown) | | Events from your own goals | High | | Events in your corridor and traditions | Medium-high | | Events from members you follow | High | | Events tagged with traditions, channels, or topics you follow | Medium-high | | Your recent engagement patterns | Medium | | Geographic relevance to your location | Medium | | Event recency (newer surfaces higher) | Decay weighting | | Event priority (HIGH > MEDIUM > LOW) | Modifier |

You can adjust these weights in Settings → Pulse Preferences. The defaults are reasonable for most members; the controls exist for fine-tuning.

6. Delivery surfaces

The Pulse delivers events through four surfaces:

7. Persistence and data retention

8. External integrations (Phase 1 and beyond)

The Pulse has three external integration surfaces:

Outlet API (Phase 1 — partners → Circlworld)

Outlets push events into the Circlworld event bus through authenticated API calls. Examples:

All Outlet API calls are:

Outbound Webhooks (Phase 3 — Circlworld → partners)

With your explicit consent, partners can subscribe to specific event categories about you. Examples:

You control which partners can subscribe to which event categories about you. You can revoke at any time.

Public Statistics API (Phase 1)

Aggregate statistics exposed without authentication. Total members, total circles, total capital coordinated, regional distribution. Used by:

Individual members are never identifiable in the Public Statistics API.

9. Data minimisation

The Pulse follows data minimisation principles:

10. Your controls

In Settings → Pulse Preferences, you can:

11. Member rights

You have the right to:

12. Audit and transparency

Version history:

EOF