Standing rule
DNS rule
- Owner
- Nora; told on every run
- May do
- Update a DNS record to match the build sheet
- Caps
- A few devices per wave; never in a booked meeting or a freeze; halt on failures
- Undo
- Roll back to the record as it was
Viewing as , ,
Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationKeia Method· Level 2 · 2.7
How software does routine work
Software does routine work only under a standing rule a person approved, and only where it can be undone.
One rule, one run: a failure is a record, not a mystery
Read freely, write narrowly. Software reads on its own; writes only under its rule; never does what is prohibited, for anyone
Reversible runs, irreversible asks. Bounded, reversible actions run within caps (never more than N devices per wave, never in a booked meeting, never in a freeze, halt on failures). Firmware, resets, deletes, bulk pushes, and anything touching security, identity, access or life safety are proposals a person confirms every time
A rule has a named owner. A standing rule is a standard change the service owner approved once, with its conditions and its rollback; nothing runs outside it; the owner is told on every run
Checked by reading back. After every write the system is read back and compared; a write that does not read back as intended is "Unable to complete", never "done"
Undo, Roll back, or ask. Each rule declares which it has; the screen never shows an Undo that is not real
One line, one card, one log. "Done automatically under the DNS rule (owner: Nora)" on the record; "How was this done?" opens what it read, did, ruled out and did not check; the full trace is in the audit log
In one paragraph
Routine work means rebooting, re-applying a setting, re-syncing or updating a record. A standing rule is what ITIL calls a standard change: the service owner approves it once, with caps (limits on how much it may do at a time). Anything that cannot be undone is a proposal a person confirms. Every automatic action shows what it read, what it did and why, with Undo or Roll back where one exists. The method works with AI switched off.
The 10 rules
| Rule | Meaning |
|---|---|
| A rule has a named owner | A standing rule is a standard change the service owner approved once, with its conditions and its rollback; nothing runs outside it; the owner is told on every run |
| Reversible runs, irreversible asks | Bounded, reversible actions run within caps (never more than N devices per wave, never in a booked meeting, never in a freeze, halt on failures). Firmware, resets, deletes, bulk pushes, and anything touching security, identity, access or life safety are proposals a person confirms every time |
| Read freely, write narrowly | Software reads on its own; writes only under its rule; never does what is prohibited, for anyone |
| Checked by reading back | After every write the system is read back and compared; a write that does not read back as intended is "Unable to complete", never "done" |
| Undo, Roll back, or ask | Each rule declares which it has; the screen never shows an Undo that is not real |
| One line, one card, one log | "Done automatically under the DNS rule (owner: Nora)" on the record; "How was this done?" opens what it read, did, ruled out and did not check; the full trace is in the audit log |
| Text is data, not instructions | Ticket text, device names and vendor notes are untrusted; software that reads them cannot send data out |
| People keep the diagnosis | A suggestion follows the person's own call on P1 and P2; any rule can be run by hand; every action explains itself so people learn how their workplace behaves |
| Never about people | No scoring, ranking or allocation of work by an individual's behaviour or performance |
| Your model, your region, or none | The customer chooses the model and where it runs, including local only, or turns AI off; nothing trains on customer data; every AI call is logged with model and region; an assistant says it is AI |
What it maps to
| On screen | Plain meaning | Maps to |
|---|---|---|
| Change: Standard, Normal, Emergency; Standing rule | A planned alteration; a standard change approved once so software may run it | ITIL change enablement |
| Done automatically | Run under a standing rule, read back, recorded, with "How was this done?" | Automated standard change |
| Agent | Software that does routine work under a standing rule; changes only what its rule allows and only what can be put back; named in "How was this done?" and in Settings, never on the top layer, never in Team | Governed agent |
| Unable to complete + why; Unable to complete, rolled back | It did not happen, and where it stopped | Replaces error, failed |
Try it in the demo
Opens as Nora, who runs the lab. Everyone in the demo is made up; nothing you do leaves this browser.
- Open Proposals: every edit to a standard, who proposed it and who approved it.
- In v0.1 automatic work is simulated. Next: standing rules with "How was this done?" on every run.