Docs/Examples and implementation patterns
examplePackage manifestv2.0.5

example.organization-planning-agenda

Reference agenda workflow for ContractSpec organization-planning contracts.

@lssm-tech/example.organization-planning-agenda
Markdown ↓Structured data ↓
Source, release and verification context

Source snapshot bcc79fcc · Declared package version 2.0.5. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.

Package source ↗ Manifest ↗
servernode
EXPLORE THE PACKAGE

See where this package fits.

Follow a declared connection, inspect an import, then open the source guide when you need the detail.

THIS PACKAGEexample.organization-planning-agendaExamples

Arrows point from a package to its direct dependency. Each count is derived from the captured manifests.

6 declarationsSELECT TO INSPECT
PACKAGE GUIDERead at source ↗

@lssm-tech/example.organization-planning-agenda

Buildable OPA OS example for the local/manual Organization Planning Agenda loop.

What this demonstrates

  • Hackathon EOD Mission Relay-style day plan generation.
  • NDconsulting-style agenda generation with private context redaction.
  • Axoperf-style deployment planning constraints and blocker evidence.
  • Customer-facing booking proposals blocked behind human approval.
  • Rich calendar roadmap lanes for focus blocks, agendas, booking proposals, approval gates, and audit artifacts.
  • Notion-ready markdown and audit payloads without calendar/provider writes.

Flagship surface matrix proof

The exported organizationPlanningAgendaSurfaceMatrixProof fixture documents the three flagship rows consumed by app smoke tests and docs:

Vertical Web monolith Mobile demo Examples/docs Managed CompanyOS seam
Hackathon EOD /companyos/opa-os consumes buildManagedCompanyOsOpaOsProof from @lssm-tech/bundle.managed-companyos. mobile.opa.hackathon_eod.native consumes the managed OPA view model. Smoke fixture renders the day plan, markdown, approvals, and evidence IDs. managed-companyos.view-model.organization-planning.hackathon-eod
NDconsulting mission /companyos/opa-os renders the client mission agenda from the managed bundle proof. mobile.opa.ndconsulting_mission.native shows agenda and approval-denial state. Smoke fixture proves agenda plus next meeting proposal. managed-companyos.view-model.organization-planning.ndconsulting-mission
Axoperf deployment /companyos/opa-os keeps deployment blocker proof in provider-blocked/degraded mode. mobile.opa.axoperf_deployment.native shows blocker priority and approval-only booking slots. Smoke fixture documents blocker outputs and evidence IDs. managed-companyos.view-model.organization-planning.axoperf-deployment
  • Rich calendar proof: organizationPlanningRichCalendarRoadmapProof exports provider-free lanes and approval-blocked calendar items for docs, sandbox, and managed-bundle consumers.
  • Web proof: packages/apps/web-application-monolith/src/opa-os-route.test.tsx validates that /companyos/opa-os consumes the managed bundle proof, emits redacted behavior signals, and keeps external effects approval-blocked.
  • Static safety: run bun run opa-os:safety from the repository root to verify the OPA no-provider, no-raw-secret, and no-live-send boundary before release handoff.

Running locally

From examples/organization-planning-agenda:

  • bun run build
  • bun run typecheck
  • bun run test
  • bun run smoke
  • bun run preflight

Boundary

This example is intentionally local and manual. It does not import provider SDKs, write calendars, send client messages, or approve external effects.

Declaration builds use build:types through the shared Bun tool; build runs bundle and declaration generation. Declared exports are preserved. Generated artifacts exclude test-only files; tests/typecheck remain separate gates.

Declared capabilities.

This manifest does not declare a capability catalogue. Use the guide, import map and source to assess the package.

Imports and export paths.

7 entries

These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.

7 imports

@lssm-tech/example.organization-planning-agenda
./src/index.ts
@lssm-tech/example.organization-planning-agenda/example
./src/example.ts
@lssm-tech/example.organization-planning-agenda/ui/organization-planning-agenda-preview.data
./src/ui.data.ts

Dependencies and related packages.

Runtime dependencies 6
react
catalog:
react-dom
catalog:
Development dependencies 6
@types/react
catalog:types
@types/react-dom
catalog:types
happy-dom
catalog:testing
typescript
catalog:

Package scripts.

Commands declared by this package. Review its setup requirements before running them; no command here was executed by this review.

buildcontractspec-bun-build build
typechecktsgo --noEmit
testbun test
smokebun test src/example.smoke.test.ts
preflightbun run build && bun run typecheck && bun run test && bun run smoke
build:bundlecontractspec-bun-build transpile
build:typescontractspec-bun-build types
← Package directoryMore in Examples and implementation patterns →
Your view

Make room for your context.

Shape the presentation around this moment. You can change it whenever you need.

Your context

The different parts of you

Choose a starting point

A useful mix of context, visuals and gentle guidance.

Tune each dimension
Each dimension can change independently. Product permissions and available actions stay unchanged.

Support the way you begin and return

Tune your support

Reading comfort

Choose your language

Interface language changes text only. Markets, prices and workflows keep their own settings.

Translation coverage

Original source

Navigation151
Graph616
Categories378
Portfolio833
Examples2,035
Source preview1,542

More translations will be added as content is reviewed.

This preference is saved on this browser.

Search the website

Useful starting points

No results. Try a shorter phrase, an operation name or another search area.

A LITTLE ROOM TO EXPLORE

Find something to explore.

Open a closer look on this page, try a different perspective, or follow the detail into its own page.

How previews and controls work
01

Look before you leave

Hover a link or focus it with Tab to see a preview. Clicking the original link or pressing Enter always opens its destination.

02

Stay with the context

Move into the preview to explore its sections. Use Alt + ↓ from a focused link to enter it with the keyboard. Escape closes it.

03

Open the possibilities

Disclosure rows, perspective choices and highlighted controls reveal more. Your view changes reading comfort and the context you explore.

A separate button for a closer look

Show small preview buttons beside links where there is room. Tap the eye to inspect, or tap the link to go straight there. This choice stays in this tab.

No browsing history is collected. Reduced motion follows your device and Your view.