Area guide · 82 packages · Follow a minimal operation end to end
Examples and implementation patterns
Learn from maintained source and fixtures, then adapt the smallest pattern that demonstrates the behavior you need.
What are you trying to do?
- Which example teaches my task?
- Is this a source walkthrough, fixture or rich preview?
- What must change when moving the example into my product?
Why start with these packages
Suggested entry point
@lssm-tech/module.examplesUse catalog-only discovery, then load runtime/host ports when a rich preview is needed.
Suggested entry point
@lssm-tech/example.minimalStart with the maintained user-contract source and its small feature/handler structure.
Suggested entry point
@lssm-tech/example.data-grid-showcaseInspect the maintained table showcase and its declared source surfaces.
Suggested entry point
@lssm-tech/example.policy-safe-knowledge-assistantExplore the source pattern for knowledge retrieval combined with policy boundaries.
Practical steps
Step 01
Read the smallest complete slice
Open the example’s declared entry and feature, follow one operation into its handler, and identify the selected transport or UI. Compare its manifest to the actual available files before copying a capability claim.
Step 02
Reproduce within the declared scope
Use the example package’s actual scripts and prerequisites from its package reference. Record the source/package versions and which checks ran. Keep external-provider and deployment qualification separate from local deterministic behavior.
Step 03
Adapt one boundary at a time
Replace the fixture’s store, authority, provider or host with your intended implementation while retaining the contract behavior and relevant negative cases. Link the resulting product guide to the source pattern and state the additional dependencies you introduced.
Choose by the behavior you need
Begin with a concrete job: define a first operation, inspect an approval boundary, render a data grid, retrieve knowledge safely or compose a feature. The minimal package exposes a user contract, feature, example entry and handler-oriented source. DataGridShowcase is the registry’s canonical table showcase. Other examples cover agent, integration, workflow and domain scenarios. Read the declared surfaces and prerequisites before choosing; a broad registry helps discovery, while a focused walkthrough should explain the important decisions and failure cases.
Use the catalog without loading every runtime
The examples module provides metadata-only catalog discovery and a separate runtime surface for rich template previews. Apps render specific examples through named host ports rather than directly importing example packages across the layer boundary. Rich UI is loaded only where the package exposes the appropriate surface. This separation makes a catalog card, source link, runtime fixture and interactive preview distinct deliverables. The 91 example-directory workspaces in the package inventory also include registry/shared/test support, so they are not 91 independently qualified product demos.
Adapt an evidence-bearing pattern
For each selected example, identify the exact contract, handler, adapter, data source and host behavior. List what remains supplied by the surrounding product: identity, persistence, provider credentials, authority, UI shell or background execution. Preserve useful negative cases such as invalid input, denied scope or missing provider. Source presence establishes an inspectable pattern; it does not establish public package installation, an executed fixture, a successful provider call or production readiness. Keep those evidence states visible when publishing an example page.
Follow a practical path.
Read the smallest complete slice
Open the example’s declared entry and feature, follow one operation into its handler, and identify the selected transport or UI. Compare its manifest to the actual available files before copying a capability claim.
Reproduce within the declared scope
Use the example package’s actual scripts and prerequisites from its package reference. Record the source/package versions and which checks ran. Keep external-provider and deployment qualification separate from local deterministic behavior.
Adapt one boundary at a time
Replace the fixture’s store, authority, provider or host with your intended implementation while retaining the contract behavior and relevant negative cases. Link the resulting product guide to the source pattern and state the additional dependencies you introduced.
Packages in this area (82)
82 of 82 shown
- Open manual →
Reference applications showing how to compose durable ContractSpec agents.
- Open manual →
Agent Console example - AI agent orchestration with tools, runs, and logs
- Open manual →
Agent Workflow Command Center - All-in-one operator cockpit for supervised AI agents in business workflows
- Open manual →
Focused AI chat assistant template with MCP tools, reasoning, chain of thought, sources, and suggestions.
- Open manual →
AI support bot example: classify and resolve a support ticket using @lssm-tech/lib.support-bot.
- Open manual →
Analytics Dashboard example with widgets and query engine for ContractSpec
- Open manual →
Rich AuthOS command center template for identity, MFA, organizations, Better Auth bridge planning, and Connect with LSSM.
- Open manual →
Smallest BillingOS French SME quote-to-cash replay proof without providers or production PA submission.
- Open manual →
Google Calendar integration example: list and create events.
- Open manual →
Standalone CommunicationOS examples, fixtures, and replay proof for external adopter flows.
- Open manual →
CompanyOS AI OS deterministic sandbox proofs for generic, EngineeringOS, support-to-product, and Incident Brain scenarios.
- Open manual →
Deterministic provider-free CompanyOS request-to-verified-proof example with explicit approvals and loopback-only evidence.
- Open manual →
Deterministic combined CompanyOS and CommunicationOS operating cockpit example for governed conversation-to-work loops.
- Open manual →
Vertical-neutral, no-network composed conformance fixture for the GTM Learning Loop, plus two fake research-provider adapters for Harness scenario execution.
- Open manual →
Deterministic CompanyOS V1 operating review replay using public spec and pure runtime APIs.
- Open manual →
Deterministic CompanyOS VoiceOps workbench example adapted from the Hackathon Voice AI UI/UX ingest lane.
- Open manual →
Content generation example using @lssm-tech/lib.content-gen.
- Open manual →
CRM Pipeline - Contacts, Companies, Deals, Tasks
- Open manual →
UX wiring proof: useContractQuery → QueryState → design-system components, all lifecycle states.
- Open manual →
Focused data-grid example for ContractSpec table capabilities
Inspect the maintained table showcase and its declared source surfaces.
- Open manual →
CommunicationOS-shaped draft-and-send reference agent: draft a message, wait for approval, then send it through an approval-gated ContractSpec operation.
- Open manual →
Gmail integration example: inbound threads and outbound messages.
- Open manual →
Deterministic all-nine Feature Hub composition reference for web and React Native hosts.
- Open manual →
Deterministic finance operations AI workflow example with human review, fixed rules, and synthetic data only.
- Open manual →
Focused ContractSpec form example and template covering field kinds, conditional rules, and layout flows.
- Open manual →
Cross-vertical finance campaign using ContractSpec gamification primitives.
- Open manual →
Interactive graph-richness showcase for ContractSpec P6 primitives: mini-map, focus-mode, custom renderers, edge labels, animations, and drilldown.
- Open manual →
Focused harness example for ContractSpec scenarios, suites, orchestration, and runtime adapters.
- Open manual →
Example showing how to use DocBlock for in-app documentation for non-technical users
- Open manual →
Integration Hub example with sync engine and field mappings for ContractSpec
- Open manual →
Credential-free PayPal commerce integration example with deterministic policy handoffs.
- Open manual →
PostHog analytics integration example: capture events, run HogQL, and manage feature flags.
- Open manual →
Integration example – Stripe Payments (blueprint + workflow + tenant config).
- Open manual →
Integration example - Supabase vector store + Postgres database wiring.
- Open manual →
Example: KB update automation pipeline with HITL review and auditability.
- Open manual →
Knowledge example – Product Canon space (blueprint + tenant config + source sample + runtime helper).
- Open manual →
Ambient coach learning journey example with contextual tips and follow-up actions.
- Open manual →
Learning journey track that onboards users to the CRM pipeline example.
- Open manual →
Drill-based learning journey example with SRS, XP, and streak hooks.
- Open manual →
Standalone managed onboarding reference proof for Learning Journey scenarios.
- Open manual →
Learning journey track covering ContractSpec platform primitives.
- Open manual →
Time-bound quest/challenge learning journey example.
- Open manual →
Registry that aggregates learning journey example tracks.
- Open manual →
Learning journey track for first 30 minutes in ContractSpec Studio.
- Open manual →
Contextual coaching UI with tip cards and engagement tracking.
- Open manual →
Duolingo-style gamified learning UI for drills and quests.
- Open manual →
Developer onboarding UI with checklists and journey maps.
- Open manual →
Shared UI components and hooks for learning journey mini-apps.
- Open manual →
Example: drills + ambient coach + quests learning patterns, powered by Learning Journey (event-driven, deterministic).
- Open manual →
Lifecycle CLI demo (example): run lifecycle assessment without an HTTP server.
- Open manual →
Lifecycle dashboard example (snippet): how to call lifecycle-managed APIs and render a status card.
- Open manual →
Example: enforce locale + jurisdiction + kbSnapshotId + allowed scope for assistant calls (fail-closed).
- Open manual →
Managed CompanyOS contract edition lifecycle proof across specs, storage, runtime wiring, integrations, and examples.
- Open manual →
Marketplace example with orders, payouts, and reviews for ContractSpec
- Open manual →
Meeting recorder provider example: list meetings, transcripts, and webhooks.
- Open manual →
Safe messaging agent actions example with fixed intents, allowlisted actions, workflow dispatch, and deterministic replies.
- Open manual →
Thin messaging app example that composes reusable CommunicationOS messaging UI with deterministic fixture data.
- Open manual →
Minimal reference project demonstrating a complete ContractSpec workflow.
Start with the maintained user-contract source and its small feature/handler structure.
- Open manual →
OpenBanking Powens example: OAuth callback + webhook handler patterns (provider + workflows).
- Open manual →
Reference integration for using ContractSpec with the OpenCode CLI.
- Open manual →
Reference agenda workflow for ContractSpec organization-planning contracts.
- Open manual →
Personalization examples: behavior tracking, overlay customization, workflow extension.
- Open manual →
Deterministic neutral Layer 1 reference harness over public CompanyOS Layer 0 exports.
- Open manual →
Pocket Family Office example - personal finance automation with open banking
- Open manual →
All-in-one template example: policy-safe knowledge assistant with locale/jurisdiction gating, versioned KB snapshots, HITL update pipeline, and learning hub.
Explore the source pattern for knowledge retrieval combined with policy boundaries.
- Open manual →
Product intent example: evidence ingestion and prompt-ready outputs.
- Open manual →
Project management sync example: Linear, Jira, and Notion work item creation.
- Open manual →
SaaS Boilerplate - Users, Orgs, Projects, Billing, Settings
- Open manual →
Service Business OS example (clients, quotes, jobs, invoices) for ContractSpec
- Open manual →
French fake-data Special Ops Cockpit template for mission dashboards, private daily journals, review workflows, playbooks, weekly reporting, AI governance, and roadmap planning.
- Open manual →
Team Hub example with spaces, tasks, rituals, and announcements
- Open manual →
Example: curated, versioned knowledge base with immutable sources, rule versions, and published snapshots.
- Open manual →
Generate API documentation videos from contract spec definitions using the ApiOverview composition.
- Open manual →
Generate terminal demo videos from CLI walkthroughs using the TerminalDemo composition and ScriptGenerator.
- Open manual →
Generate short-form marketing videos from content briefs using the video-gen pipeline.
- Open manual →
Focused visualization showcase for ContractSpec primitives and design-system wrappers
- Open manual →
Voice provider example: Gradium and Fal text-to-speech integration patterns.
- Open manual →
VoiceOps operating graph example: conversation → governed operating graph (DataViewGraphSpec canary replacing hackathon GraphCanvas)
- Open manual →
Wealth Snapshot mini-app for accounts, assets, liabilities, and goals
- Open manual →
Workflow and approval system example for ContractSpec - State machine with role-based transitions
- Open manual →
Shared UI examples demonstrating reusable ContractSpec component composition.
- Open manual →
Example contract specifications collection
Use catalog-only discovery, then load runtime/host ports when a rich preview is needed.
Curated but no longer in the workspace: example.app-submission-readiness-mobile-proof, example.authos-user-relation-graph, example.companyos-knowledge-graph, example.contract-graph, example.creator-platform-ai-native, example.creator-platform-foundation, example.gtm-provider-recipes, example.osint-proof, example.shim-delete-ci
What connects to this area
Core contracts
Recognize the contract, handler and adapter responsibilities in an example.
Runtime adapters
Know which host and execution path the example actually uses.
Ui and presentations
Table, RoleMorph and other UI examples illuminate rendering boundaries.
Agents and context
Agent examples need context, provider and tool evidence of their own.