Guard Rails, Costs, and What Is Unproven
Guard Rails, Costs, and What Is Unproven
What is guaranteed about children's data, and the one place an agent reads it; the record of what agents change; the costs of the arrangement, review resting on very few people and documents drifting from the code; and what is proposed, unmeasured or undecided. Closes the software part of the series.
Children's data. The rule for agents that write code
is that they test with made-up children, never with a real child's
record. The exception is feedback. A report sent from a lesson can
hold a child's words or a picture of the screen, and the feedback
A record of what agents do. Every change to the code keeps its history, and a change that a routine or the studio proposes names who asked for it. Every change an agent makes to shared records through the server, such as answering a report, is logged under the agent's name, and so are routine starts and pauses. The log is never pruned. A check refuses any new part of the server that would change records without logging it, unless it states why it needs no entry.
What it costs. Review rests on very few people: today almost every change waits for one reviewer. Sharing review out by area is the target, not yet in place. Documents and code also drift apart. Checks catch a design document left marked as a proposal for too long, not one whose content has fallen behind the code.
What is unproven. That no scheduled agent merges rests today on its written rules and on review; an account for the routines that cannot merge at all is proposed. We do not yet measure how often a person has to step in for each finished piece of work. Whether some small changes could ever be merged without a person was examined and, for now, rejected.
This article completes the software part of How Fido Is Built. The part on running the school begins with Fido's Bet and How We Will Know, and Who Fido Is For, and What It Owes opens the part on whom it serves.
Questions, objections, or keen to help build it? Write to us.