Meet DDS-01: letters from Bishop
A blue mailbox on treads, cheerful letters from a friend, and room for Ash to choose. The DDS-01 correspondence design is recorded; implementation and testing are still ahead.
Ash’s world is getting a postal service—on the drawing board. DDS-01, the Droid Delivery Service, is planned as a little blue post office mailbox on treads, with large expressive eyes and a friendly arrival chime. Its first job will be bringing letters from Bishop, Ash’s fellow Recon Chinchilla and friend out in the field.
The design keeps three distinct characters. Bishop writes the letters, DDS delivers them, and Ash decides whether to read, acknowledge or reply. DDS remains separate from Ash’s core system and cannot take over his choices or change his personality. Delivering a letter is an invitation to connect.
PMA—positive mental attitude—guides the character. DDS should be kind, patient, curious and never hostile, malicious, hateful or spiteful. Happy, excited, curious, patient and sleepy eyes will carry its personality. A blocked path calls for patience, not anger. Nobody has to feel cheerful or respond on demand. These are design requirements that still need to be tested.
The incoming schedule allows one Bishop letter each week. Monday gets a 25% chance of delivery. If no letter arrives, Wednesday gets another 25% chance. If neither day succeeds, Friday is the guaranteed delivery day in the planned schedule. Once the week’s letter arrives, the remaining incoming slots are canceled. A failed delivery must remain pending or failed in the record; the schedule alone cannot prove that a letter arrived.
DDS is off regular duty on Saturday and Sunday. Each day independently has a 50% chance to offer Ash an opportunity to write back. Ash chooses whether to use it, and DDS can handle the special outgoing request if he does. A Saturday reply does not remove Sunday’s opportunity. There is no pressure to write and no repeated roll to force a response.
Bishop’s letters will be cheerful stories from the fictional field: small discoveries, interesting places, gentle humor and reminders that he misses Ash and looks forward to seeing him again. Occasionally he will ask whether CODD is actually delivering coffee, or how the Unknown Engineer is doing. Those familiar references should feel like a friend checking in, not a repeated script.
Trips will give the letters a little shared history. When Ash visits a location, a notice will make that trip available for Bishop’s next letter. The latest location wins: if Ash visits somewhere else before the letter is generated, the newer visit replaces the older pending one. Bishop asks how that most recent trip went, and the notice is consumed without building a backlog of old questions.
If there is no new visit when the next letter is written, Bishop gently reminds Ash to take some time off or see somewhere new. It is encouragement from a friend, never an instruction to leave or a reason to feel guilty.
The engineering plan calls for event records of schedule decisions, letters, delivery outcomes, Ash’s reply choices and location notices. Tests will simulate a full week and weekend, check the probability boundaries, and exercise failed handoffs, retries and restarts. We will also review the eyes, arrival behavior and letter tone, and verify that Ash’s choices remain his own.
The controlled design is now in the Project Book. DDS software, artwork and animation, persistence, integration and deployment have not been completed, and its acceptance tests have not been run. This journal entry records the plan; DDS is not yet an active feature in the public Command Center. The next step is an isolated software prototype and a simulated week of correspondence.