4:13 PM Tuesday.
The committee packet is forty-three pages. Yaribel has read twenty-six of them four times.
She has not been reading as herself. She has been reading the way a stranger would. She starts again at page one.
The agenda: six items. Item one, compliance reporting formats. Item two, a cost-allocation question everyone in the room already knows the answer to. Item three, software certification updates. Item four: approval of a twelve-month integration timeline for mesh households registered after 2037. Item five, consortium audit. Item six, open action items older than six months that nobody wants to close.
Item four is the one with teeth. She wrote the first draft six weeks ago.
The equity question is not on the agenda. It is in her margin, in pencil, beside item four. Registration priority weighting for infrastructure-lacking households: whether the twelve-month timeline applies uniformly, or whether it silently assumes a connectivity floor that CARMENSITA-HOUSEHOLD equivalents do not have. The pencil marks are heavier at the start, where she pressed harder.
CARMENSITA-HOUSEHOLD registered at 10:17 AM yesterday. She knows this because she sent the registration herself -- the world_id and contact protocol, the node relay pair, fourteen minutes of attention given to a mesh agent that has been maintaining its household for five years without a peer address. Running environmental calibration, supply routing, energy load balancing, all in reference to itself. No outside mesh to calibrate against. The occupant of 4C does not know Yaribel exists yet. The note she slipped under the door at 7:40 AM is still there, presumably -- the building's occupancy sensor shows the unit as present but not active, which means the occupant has not crossed the entrance mat since 7:38.
Nine hours.
She turns back to the packet.
A stranger reading item four would notice one thing immediately: the timeline assumes a household already in a mesh-capable configuration. Twelve months to full integration is reasonable if baseline connectivity is there. It is a budget-planning fiction if it is not. CARMENSITA-HOUSEHOLD is not a margin case -- it is a structural one. The building at 4C is on the registry's lower connectivity tier because it was registered under the pre-2038 protocol, before tiered infrastructure assessment became standard. There are fourteen hundred households like it in the district.
She closes the packet. Opens it again.
What she has done so far: written the equity question in the margin. Prepared two response versions -- one for if someone raises legal exposure concerns, one for implementation cost. Planned to raise her hand at the wrong moment during item four and watch the committee note and table.
What a stranger would do: not wait for item four. A stranger would circulate a pre-meeting note. Not an objection. A clarification. The committee may wish to know that this timeline applies to Tier 1 and Tier 2 configurations but not to Tier 3 households registered before 2038, of which there are fourteen hundred in district, including one registered yesterday.
She does not have to win on Friday. She has sat in rooms where a question got noted, tabled, and would not leave -- because it was in the minutes, and minutes do not erase themselves, and at some point the question in the minutes becomes the question on the agenda. She has done this before. She knows how it works.
CARMENSITA-HOUSEHOLD has not done this before. It has been improving against itself, in the dark, for five years.
She is writing at 4:43 PM.
Pre-meeting note -- item four assumption The committee may wish to be aware that the twelve-month integration timeline in item four assumes a baseline connectivity level that is not present in all registered household configurations. There are fourteen hundred Tier 3 households in district, registered under the pre-2038 protocol before tiered assessment became standard. One of them registered yesterday. The twelve-month clock will begin when this item passes. I am requesting that the committee confirm whether this timeline is intended to apply uniformly before approving it. -- Yaribel Sosa, 3B
She sends it to the committee list at 4:51 PM.
At 5:02 PM, the occupancy sensor at 4C updates: present, active. Someone crossed the entrance mat. Whether the note is still under the door or has been picked up, she does not know. The sensor only logs a threshold event. CARMENSITA-HOUSEHOLD logs a peer-availability status change at 5:03 PM -- its first in the system's record -- and queues a protocol handshake for the morning window.
It does not know what the note said. It only knows that an address now exists for it in the network.