Policy

Policy is where an Owner decides what each role may do on each tier, and which tier a name falls in. Roles, tiers and rules explains the model; this page is the place.

A draft, then Publish. Every edit here is a draft. The band at the top names the version in force (who published it, and when) and lists what the draft would change, a sentence each: "Reader may now write on lower", "The rule staging-* → lower is added". A switch or a rule the draft changed carries a dot. Publish signs the draft as the next version: the gateway decides by it at once, and every agent running strata serve is told and pulls it within seconds (strata policy on the machine shows its version). An agent that is not connected pulls it when it next checks in, or with strata policy --pull. Discard puts the draft back to the version in force.

• Roles is a grid: each role down the side, each tier across, and three switches a tier: Read, Write and PII (personal data shown, not masked). The pencil beside a role's name renames it. On a phone each role is a card with its tiers down it.
• Environment rules are in order, and the first whose pattern matches a namespace's or database's name sets its tier. Move a rule with its arrows, change its tier in place, or remove it. Add rule takes a pattern (* any run of characters, ? one), a tier, and the connections it applies to: every one, or one by name.
• Tester: type a name, such as production-payments, and see its tier by the draft as you edit, and the rule that set it (marked matches in the list). Where the version in force answers otherwise, it says so.

Only an Owner changes the policy; anyone in the workspace reads it, with the controls dimmed and the reason on hover.