Experience — User Interaction
Purpose
Section titled “Purpose”The user interaction layer. Manages consent, oversight, onboarding, accessibility, and how users engage with AI. Like accessibility services and user preferences in an OS, Experience ensures every interaction respects the user. It provides structured entry points for new operators and teams, and manages human oversight: deciding when a task requires human review versus autonomous execution.
Key interfaces
Section titled “Key interfaces”interface ExperienceResult { success: boolean; error?: string; [key: string]: unknown;}
interface ExperienceStatus { initialized: boolean; subsystems: Record<string, boolean>; // 9 subsystems state: ExperienceState;}
interface OnboardingSubsystem { team: { start(company: string, options?: Record<string, unknown>): Promise<ExperienceResult>; configure(teamId: string, config: Record<string, unknown>): Promise<ExperienceResult>; }; project: { setup(name: string, options?: Record<string, unknown>): Promise<ExperienceResult>; };}import { BaselineExperienceSystem } from '@baselineos/experience';
const exp = new BaselineExperienceSystem();
// Start a team onboarding flowconst result = await exp.onboarding.team.start({ name: 'Acme' });// { success: true, teamId: '...' }
// Check system status — all 9 subsystems report availabilityconst status = exp.getStatus();// { initialized: true, subsystems: { onboarding: true, collaboration: true, ... } }LayerSweep checks
Section titled “LayerSweep checks”The layer sweep runs three checks against Experience:
| Check | What it validates |
|---|---|
| Consent checkpoint | User has granted consent for AI processing (when user context is present) |
| Interaction logged | The layer sweep interaction is recorded in the audit log |
| Oversight routing | Epic-complexity or critical-priority tasks are routed for human review |
References
Section titled “References”- Specification: 05-experience — nine subsystems and consistent return contract
- Package README —
@baselineos/experience