Guides
Guides
End-to-end walkthroughs on the Kaiten Sushi Shop demo — gate a feature by License, meter usage to the cap, roll a feature out progressively, journal deployments from CI/CD, and answer who had access.
The core concepts explain the model one page at a time; the guides run it end to end. Each one starts from the seeded Kaiten Sushi Shop organization — four customers, three License families, entitlements with live usage — and finishes with something you can verify in the console and in the audit trail. Steps happen in the console where a console view exists, with the API equivalent one unfold away; operations your product makes at runtime — reporting usage, evaluating a flag, reading the trail — are shown as the API calls they are.
Every guide assumes $KAITEN_API and a service-account token in $KAITEN_TOKEN, set up as in the quickstart, and names the scopes it needs.
Gate a feature by License
The canonical chain: a BOOLEAN entitlement, two Licenses granting it differently, a flag whose rule reads the grant, two evaluations, both decisions in the audit trail.
Meter usage and enforce limits
Report consumption against a NUMBER grant, hit the cap, correct a counter, react to the threshold events, and design your own quota.
Progressive rollouts
One flag from a single customer to everyone — a deterministic percentage, a dated ramp, general availability, and the kill switch.
Deploy with CI/CD
Register the component version on build, cut the release, and record each landing zone by zone from your pipeline.
Answer who had access
Turn the compliance question into a filter on the instance's audit trail — events, time ranges, the cursor walk, two worked cases.
Pricing Tiers
Build a tier from one catalog of entitlements, one License per tier, and one grant per pair — the Kaiten Sushi Shop tiers as the worked example, every call verified against the API.
Gate a Feature by License
The canonical chain end to end — a BOOLEAN entitlement, two Licenses granting it differently, a flag whose rule reads the grant, two evaluations, and both decisions in the organization's audit trail.