These examples are included to show how PBC reads in practice across different levels of maturity.
-
- the canonical billing example with rich Markdown presentation and current block patterns
- good for
pbc:config, states, behaviors, rules, and polished authoring
-
- a feature flag and progressive rollout example
- good for stable configuration, precedence rules, and safe fallbacks
-
- a permissions/capability example
- good for role modeling and behavior/rule interplay
-
- a general permissions + entitlements example
- good for deny-by-default, entitlement gating, and decision outcomes
-
auth-signin-session-access.pbc.md
- an authentication and session-control example
- good for states, transitions, step-up checks, and access rules
-
- a hardware/embedded system example (nRF52840 proximity sensor)
- good for physical grounding, hardware validation dependencies, and provenance tracing
-
- an ML-pipeline example (Apple Watch → Zepp swing alignment and trained replacement models)
- good for empirical trust graduation: rules promoted to
trustedonly after passing a stated quantitative gate,provisionaluntil the evidence exists
-
- a parent-charter composition example (TennisAgent root composing the aw-zepp-alignment leaf via
pbc:include) - good for product trees: a root that owns cross-cutting behavior and delegates a leaf's rules through an explicit
ownssplit, with no overlap
- a parent-charter composition example (TennisAgent root composing the aw-zepp-alignment leaf via
All examples above are bundled in the PBC Viewer. Run the viewer to explore these contracts as interactive cards, state diagrams, and validation results instead of raw Markdown.
- Examples are illustrative, not normative.
- Some examples are more polished than others by design.
- The format allows both richly narrated documents and more compact, block-centered authoring styles.