Area guide · 24 packages · Trace a personal command and receipt
Personal workflows, learning and progress
Compose subject-controlled personal workflows and learning experiences with explicit consent, replay and progress semantics.
What are you trying to do?
- How is personal authority bound to a command?
- Which runtime owns learning progress or gamification?
- How are private records kept separate from organization views?
Why start with these packages
Suggested entry point
@lssm-tech/lib.personal-os-runtimeUse subject-bound authorization, command builders, replay and rights projections.
Suggested entry point
@lssm-tech/module.learning-journeyExplore onboarding, drills, coaching and progress adapters.
Suggested entry point
@lssm-tech/lib.gamification-runtimeInspect deterministic campaign, activity, XP, streak and replay behavior.
Suggested entry point
@lssm-tech/lib.personal-health-runtimeInspect strict consent, normalization, sync and evidence boundaries for health-domain data.
Practical steps
Step 01
Trace one personal journey
Follow a plan, household or consent action from trusted subject input through command construction, transaction and projection. Identify which records support retry and which data is visible to another actor.
Step 02
Inspect progress conversion
Choose an existing learning journey and follow its progress through serialization and the gamification adapter. Compare recurrence boundaries and repeated activities in the maintained tests before changing the stored representation.
Step 03
Review a withdrawn grant
Inspect the rights and consent path when a participant revokes access or a source connection changes. Check that derived projections, assistant context and queued work use the new authority state rather than a previously cached permission.
Bind a personal action to its subject
PersonalOS runtime supplies pure authority, autonomy, immutable-event replay and rights primitives. Hosts provide verified identity, clocks, encryption, audit, durable stores and effects. The documented transaction seam binds the command, receipt, event, encrypted snapshot, idempotency result and outbox together. Browser-safe command builders accept exact host-supplied context and preserve the declared policy. Constructing a household delegation or a personal plan does not authorize the new command through its own proposed state.
Choose learning and progress responsibilities
LearningJourney provides onboarding, drills, coaching and adaptive journey composition. Existing progress adapters preserve the Date-bearing journey state when crossing into the storage-neutral GamificationRuntime. Gamification evaluates explicit activities, cadence slots, streaks, capped XP and replay using supplied timestamps and participant references. Keep these semantics visible when migrating a learning product: converting storage shapes should not silently change timezone, rounding, recurrence or the meaning of a completed lesson.
Preserve privacy and source meaning
Personal domain packages include household, productivity, finance and health responsibilities. Their source scopes should guide what a composed product may expose. The health runtime, for example, requires explicit consent and preserves units, timestamps, source provenance and paginated sync checkpoints; conflicting provider observations remain separate evidence. Such behavior is a data-lifecycle contract, not a clinical interpretation. Product and agent projections should reveal only what the exact subject and current grant permit, including after revocation or a changed connection.
Follow a practical path.
Trace one personal journey
Follow a plan, household or consent action from trusted subject input through command construction, transaction and projection. Identify which records support retry and which data is visible to another actor.
Inspect progress conversion
Choose an existing learning journey and follow its progress through serialization and the gamification adapter. Compare recurrence boundaries and repeated activities in the maintained tests before changing the stored representation.
Review a withdrawn grant
Inspect the rights and consent path when a participant revokes access or a source connection changes. Check that derived projections, assistant context and queued work use the new authority state rather than a previously cached permission.
Packages in this area (24)
24 of 24 shown
- Open manual →
Evidence-scored PersonalOS product composition and requirements coverage.
- Open manual →
Fail-closed AuthOS and Better Auth session bridge for PersonalOS.
- Open manual →
Subject-bound PostgreSQL event, encrypted projection, rights, and outbox persistence for PersonalOS.
- Open manual →
Deterministic storage-neutral gamification evaluation and replay runtime.
Inspect deterministic campaign, activity, XP, streak and replay behavior.
- Open manual →
Portable cross-vertical gamification campaign contracts and validation.
- Open manual →
Pure fail-closed PersonalOS finance runtime.
- Open manual →
Subject-bound, provenance-first, non-advisory PersonalOS finance contracts.
- Open manual →
Pure PersonalOS health authorization, normalization, reconciliation, and sync runtime.
Inspect strict consent, normalization, sync and evidence boundaries for health-domain data.
- Open manual →
Consent, provenance, safety, sharing, and rights contracts for non-clinical PersonalOS health data.
- Open manual →
Pure fail-closed PersonalOS authority, replay, projection, and rights runtime.
Use subject-bound authorization, command builders, replay and rights projections.
- Open manual →
Consent-aware personal mission, agency goal, and projection contracts for LSSM OS.
- Open manual →
Reusable gamification projections and theme-aware React surfaces over the canonical gamification runtime.
- Open manual →
Comprehensive learning journey engine - onboarding, LMS, flashcards, gamification, and AI personalization
Explore onboarding, drills, coaching and progress adapters.
- Open manual →
Subject-bound, consent-controlled HCircle community domain runtime.
- Open manual →
Authority-first RoleMorph and reversible Personalization composition for PersonalOS surfaces.
- Open manual →
Subject-bound, non-advisory PersonalOS pocket family-office module.
- Open manual →
Consent-bound founder-private cockpit and Pactena handoff runtime for PersonalOS.
- Open manual →
Pure PersonalOS mission, goals, outcomes, and observed-metrics runtime.
- Open manual →
Subject-bound non-clinical PersonalOS health ledger orchestration.
- Open manual →
Pure PersonalOS household membership, delegation, and revocation runtime.
- Open manual →
Consent-bound PersonalOS learning adapter and reversible coaching runtime.
- Open manual →
Subject-bound PersonalOS life administration and personal knowledge runtime.
- Open manual →
Fail-closed PersonalOS performance, capacity, release, rollback, and support controls.
- Open manual →
Pure PersonalOS Today planning, habits, recovery, review, and capacity runtime.
Curated but no longer in the workspace: app.personalos-api, app.personalos-desktop, app.personalos-mobile, app.personalos-web, app.personalos-worker
What connects to this area
Identity and access
Personal actions need an exact trusted subject and delegated scope.
Schemas and results
Progress and personal records must preserve explicit units, time and provenance.
Forms and data
Personal inputs and consent-bearing records often enter through forms or exchanges.
Agents and context
Assistive agents receive only the selected, authorized personal context.