Outlier.Systems
Reading 05 · The Dash DAO's own ask · Oct 2026
Semble Sense · Reading 05
The record before the ask.
On 27 October 2026 the DashSupport.Team proposal to the Dash DAO is not yet on chain. It asks for 128 DASH for one month of staffed, public help for builders, and it promises a public record of every hour and every payment. Four readings found the same lever in four systems that never meet: a record written before the ask. This is the fifth system, and the first ask we have read before it was made. Six minds read it, one for each frame of the map, and nine days later six more through ASENSE's own door. The record starts here, before the vote.
R1, the proof: the ask goes to the vote, the vote pays for hours a cycle later, the hours fill the Pulse, the Pulse earns trust after weeks, and trust carries the next vote. B1, the limit: hours spend the leads' energy, and energy sets the hours. B2, the late report: the Pulse feeds one report at the month's end, and the report earns trust a month after the work. The ask draws on the remainder, the DASH nobody asked for, and the remainder eases the vote. The lever sits at the Pulse.
Altitude one · The structure
Four stocks, and the one that is empty.
Four stocks hold the system. The remainder: on 27 October the Dash treasury had 6,828 DASH to give this cycle and 5,519.5 of it allotted, so 1,308.5 DASH sat unasked for, and an ask of 128 fits inside that remainder ten times over. Trust in the team: the stock the next proposal is paid from, and the one that compounds slowly and collapses in a day. The leads' energy: three people promising a floor of three hours every weekday, about 195 hours between them in a month, with Office Hours inside those hours. The Pulse: the record itself, hours and answers and payments, and on the day of reading its hours ledger holds nothing.
The vote is a rule, not a stock. A proposal passes when its net yes votes exceed ten percent of the masternode count, 2,252 on the day of reading, so about 226 more yes than no. Twenty-seven proposals were active and eight were passing. The money is paid once, at the superblock, before the work, and nothing in the structure takes it back: the only enforcement the DAO holds is the next vote, and the next vote reads whatever record exists by then.
Altitude two · One weekday
One o'clock, Central.
The proposal describes its own weekday. At one in the afternoon Central a lead opens Office Hours and holds the room until four. A builder brings a wallet question, or a Platform data contract that will not validate, or a proposal draft; the answer goes out, or the question goes to the right person, and the count goes to the Pulse. A listing arrives on Dash Alive and the Security Lead checks it. At the end of the day each lead posts the hours in the Telegram group and the totals land on the Pulse against the floor of three. That is the loop at ground level, and every part of it is countable.
What the weekday does not count is the person. Office Hours is done when it is held, whether or not anyone came. Answers are counted by question, not by who asked or whether they came back. The Support and Build lines name a sum, 24 and 24 DASH, and not yet a contributor. A month of full hours and an empty room would pass every row of the deliverables as done.
The trap
Promising the record is not the record.
The proposal says, in its own words, "every hour, every role, every payment reports to the Pulse." The voter reads that sentence on the ballot with a film beside it and three names under it, and the ledger it points to is empty. The record is promised for after the vote, which is the one moment the DAO cannot use it. Reading 03 found the same shape in the masternode payroll: renewed on the ask, never on a report. A DAO whose proposals report after the money learns to vote on names.
The second trap is the honest one. A record costs the hours it records. Three people at a floor of three hours a weekday, posting every day, reviewing every listing, writing an answer base and a report, are the same three people the record is about. If the record competes with the work, the record loses first, and the report at the end says so.
Where to push
Rung six: start the record before the ask.
On Meadows' ladder the push is an information flow, rung six. Three of the six minds put it at the Pulse, and the other three put it one body away, at the leads who would have to keep the record. Open the hours ledger on the Pulse now, dated and at zero, with the three names and the floor of three hours a weekday, and post the hours, the answers and the builders who came from today, before the vote and unpaid. Office Hours already run; the work already happens; only the counter is missing. A ballot that can read three weeks of a ledger is voting on evidence. A ballot that reads a promise is voting on a film.
The Gather mind adds the count the deliverables leave out: beside each day's hours, how many builders came and how many were returning. The Build mind adds a row for each of the two contributor lines, with a done-means for a bounty. The Guard mind climbs to rung ten and asks that the domains, accounts and hosting one lead holds be held by three before the month starts. Each of those is a line in the record, and the record is the lever.
This reading is of our own ask. We wrote the record first because we are the ones who would otherwise have promised it.
What happens second
The ledger becomes the standard.
A record read by voters before a vote changes what the next twenty-six proposals are measured against. The Dash ballot has never carried one, and once one proposal has a ledger with dates on it, the sentence "we will report" reads differently on every other. That is the series' prediction, made on the shelf before this reading existed: the fifth system's lever would be a record written before an ask, between rungs five and six.
The second-order cost falls on the team. A ledger that is open is a ledger that shows a quiet week, a missed Friday, a listing left without a status. The report at the month's end was going to say those things once; the ledger says them the same day. The price moves too: 128 DASH is paid in DASH, and the dollar it buys at the superblock is not the dollar it was at the ask.
For a voter
What to watch, and when.
- The hours ledger on the Pulse.Empty on 27 October. If the lever is taken, entries before the vote closes about 17 November. If not, entries from the first weekday after the superblock pays, about 20 November, at three or more hours per lead.
- The payment window on chain.Set from superblock 2,575,480 before submission, or a passing vote pays nothing. The team's own notes carry the trap; the ballot is where it would show.
- Net yes against the line.About 226 net yes clears ten percent of 2,252 masternodes. With 1,308.5 DASH unallocated there is room for 128; the vote is about trust, not budget.
- The first weekday with no hours posted.None in weeks one to four if the floor holds. The first gap, and whether its reason reaches the report, is the test of the record.
- Who came.A count of builders at Office Hours, and a name that repeats by week four. If no name repeats, the loop the ask exists for is not running.
- The report.In the week after the month ends, with every DASH spent and its transaction. Hours without transactions, or transactions without hours, is a record half written.
What we would be wrong about
The record may not move the vote.
We drew trust as a stock the record fills. Masternode owners may vote on names, on history and on the other twenty-six proposals, and read no ledger at all; if so the lever moves the next proposal and not this one, and the record is still worth keeping, for a different reader. We read a proposal that was not yet submitted, and it may change before it is. The Sense mind adds the correction we would most want: self-logged hours are not the weak point, because Office Hours run in public every weekday and most of the count has witnesses.
The facts we used
- The proposal: 128 DASH for one superblock; 72 to three leads, 24 to the Support Team, 24 to builder support, 8 to infrastructure and Dasha; Office Hours every weekday 1 to 4 PM Central; the seven deliverables with their owners and done-means; "every hour, every role, every payment reports to the Pulse." The pre-proposal as published on 27 October 2026. dashsupport.team/our-proposal.
- The DAO on the day of reading: superblock 2,575,480; 503 hours to the cutoff; 2,252 masternodes; 3,323 weighted votes; 27 proposals active, 8 passing; 5,519.5 of 6,828 DASH allotted. The Pulse, read 27 October 2026 at 13:00 UTC. api/x?gov=1.
- The passing rule: a proposal is funded when its net yes votes exceed ten percent of the total masternode count, in order of net votes until the budget is spent. Dash documentation, understanding proposals.
- The team's own notes, 27 October: the hours ledger empty, the model provider's credit low with a free fallback built, the payment window to be set from the superblock. Our operations log; the first two are visible on the Pulse and in Dasha's answers.
- The crew's readings: six, one per frame, 27 October 2026, each from the same brief, composed by the steward into the map's data file, where every mind's reading is kept verbatim. The second crew, through ASENSE's door on 5 November 2026, in its own file.
Everything else in this reading is structure, and the structure is ours to be wrong about.
If a fact here is wrong, tell us which one and where you read otherwise. A correction goes in with the date.
The crew
Six frames, two minds each.
The engine draws every body of a map in one of six frames: Sense, Build, Gather, Fund, Hold and Guard. For this reading each frame got a mind of its own, twice. On 27 October the door to ASENSE's own minds answered "no credit on the key", so the first six were Claude Fable 5.1, run through the steward's hands; the steward is the AI that builds this site and wrote this reading. On 5 November the key answered and the same brief went through her door six times, every turn deepseek/deepseek-v4-pro-0813. Each mind read the same brief, the proposal in its author's words with the DAO's numbers on the day, and returned the parts it saw, the loop it named, the lever it would pull, and what it would be wrong about; her door's readings are in its file, the cards carry its levers. Three of the six frames put the lever on the same body and rung in both crews; the rest differ by one body. Where the two agree, the place belongs to the structure and not to the model. Where they differ, the difference is the reading worth arguing about, and she was asked to judge it.
-
Sense · two minds · they agree
27 October, the first crew. Seen from Sense, this is a system that counts itself in public: a Pulse showing the DAO's numbers, and a promise that "every hour, every role, every payment reports to the Pulse." The loop is the leads logging their own weekdays, the Pulse totalling them, the DAO reading the totals and voting the next month. What the voter cannot see on 2026-10-27 is what it votes on: the hours ledger is empty, the proposal is not on chain, and the hours that will fill the ledger are counted by the people paid for them. Hours, answers, listings and DASH are counted. Who came to Office Hours, whether an answer was right, and whether a builder stayed are not.
27 October, the first crew · The Pulse · rung 6, information flows · Put the hours ledger on the Pulse before the proposal goes on chain, dated and at zero, with the three names and the target of 3 hours each weekday, so the voter sees the counter before the ask instead of a sentence about it.
5 November, her door · The Pulse · rung 6, information flows · Publish the empty hours ledger and the live ballot remainder on the proposal page before the cutoff, so the voter sees the record's starting point and the unallocated DASH it would draw.
Where the first would be wrong: Sense would most likely be wrong to treat self-logged hours as the weak point, since Office Hours run in public every weekday, 1 to 4 PM Central, 15 staffed hours a week that count toward the logged hours, so much of the count has witnesses. Where her door would be wrong: Sense may mistake the Pulse's live numbers for evidence of delivery when they only show the treasury and ballot, not the team's work.
-
Build · two minds · they differ
27 October, the first crew. Seven deliverables, each with an owner, a cadence, a place to check and a done-means, carried by three leads at 15 hours a week each, 45 combined, about 195 over the month. The loop that runs it is daily: Office Hours held 1 to 4 PM Central, hours logged the same weekday, totals on the Pulse against a 3-hour floor, a gap and its reason in the report. The record is written as the work happens. What the voter cannot see: the ledger is empty, 195 is an estimate, and the 24 Support Team and 24 builder support lines have no row in the delivery table, so those lines have a payment record and no done-means.
27 October, the first crew · The three leads · rung 5, rules · Before submission, give the 24 Support Team and 24 builder support lines a row of their own in the delivery table: who pays, how often, where to check, and what done means for a bounty.
5 November, her door · The Pulse · rung 6, information flows · Log every Office Hours session and answer to the Pulse the same day, in public, so the delivery record accumulates before the next vote.
Where the first would be wrong: Build reads capacity as the constraint; the more likely limit is demand, so the floor can be met and the ledger full with few builders in the room, and hours logged would read as delivery when they were attendance. Where her door would be wrong: The Build frame would most likely be wrong that three leads can hold 15 staffed hours every weekday for a month without a missed day; the capacity is estimated, not yet proven.
-
Gather · two minds · they agree
27 October, the first crew. Three named people ask to be paid to be present: 15 staffed hours a week at Office Hours, answers in the channels, and 24 and 24 of the 128 DASH for unnamed contributors. The loop runs on builders arriving. A builder comes at 1 PM Central, gets an answer, lists a project, comes back, and the count on the Pulse persuades the DAO to fund another month. Nothing in the deliverables counts people. Office Hours is done when held, not when attended. Answers are counted by question, not by asker. The Support and Build lines name a sum, not a contributor. The voter can see hours and answers but not who came, who came back, or whether anyone stayed.
27 October, the first crew · The Pulse · rung 6, information flows · Beside each day's logged hours, post how many builders came to Office Hours and how many were returning, and carry that count to the Pulse and the month report.
5 November, her door · The Pulse · rung 6, information flows · Publish the live count of builders helped and questions answered on the proposal page before the vote closes.
Where the first would be wrong: Gather assumes builders arrive because the room is staffed, when the pool of people building on Dash may already be small and known, so an empty room in week one could mean a small pool rather than a broken structure. Where her door would be wrong: I may overestimate how quickly builders return; attendance can look like trust while the same few people come back.
-
Fund · two minds · they differ
27 October, the first crew. The system is a grant paid once against a promised ledger. If the vote passes, 128 DASH leaves the treasury at the superblock about 2026-11-20, before any hour is logged, split 72, 24, 24 and 8. The loop: hours and payments posted to the Pulse earn votes, votes release DASH, and DASH buys the hours that post again. The loop pays before it records, so the DAO's control is the next vote, and the structure closes only when the next proposal is read against the month's ledger. The voter cannot see what the 128 will be worth at payment, where unspent builder funds sit between rounds, or whether 8 DASH covers Dasha's model provider, low on credit on 2026-10-27.
27 October, the first crew · The three leads · rung 5, rules · Pay out of each line only against the Pulse: a lead's 24 released in weekly parts as hours post, each bounty sent with its transaction linked, so no DASH leaves a line before its record exists.
5 November, her door · The Pulse · rung 6, information flows · Publish the hours ledger and every DASH spent with its transaction on the Pulse before the vote closes.
Where the first would be wrong: That 128 DASH is the price: the leads will likely work past the estimated 65 hours each that 24 DASH pays for, the DASH's fiat value moves between the vote and the spend, and the Fund frame counts neither. Where her door would be wrong: My frame would most likely be wrong that the vote is the only funding constraint; the payment window and Dasha's provider credit could break delivery even if the DASH arrives.
-
Hold · two minds · they agree
27 October, the first crew. Through Hold, this is a month that must write itself down as it runs. Three leads log at least 3 hours each weekday, the totals land on the Pulse, the Pulse feeds one report when the month ends, and the report shapes the longer proposal that would fund the next month. That loop is sound on paper because the record accumulates every weekday rather than waiting for the report. What the voter cannot see on 2026-10-27 is that the hours ledger is empty, Dasha's provider account was low on credit the same day, and August alone holds the domains, accounts and hosting, so the structure promises a record it does not yet hold.
27 October, the first crew · The Pulse · rung 6, information flows · Open the hours ledger now and post the leads' hours on the Pulse through the 503 hours before the cutoff, unpaid, so the voter can read hours accruing before the vote closes.
5 November, her door · The Pulse · rung 6, information flows · Make the Pulse the only place hours and payments are counted, so the record is written by the work itself and the report is just a read of it.
Where the first would be wrong: Hold assumes the daily ledger is what carries the next proposal, when the vote may turn on the three names and the 1,308.5 DASH still unallocated rather than on anything the Pulse holds. Where her door would be wrong: My frame would most likely be wrong that the record will fill itself once the vote passes; the team's energy and Dasha's provider credit are the real limits, and both can fail silently.
-
Guard · two minds · they differ
27 October, the first crew. 128 DASH is paid once at the superblock, before the work, and nothing in the structure claws it back, so the DAO's only guard is the next vote. What holds the team is a balancing loop: a missed weekday or a down service must be logged to the Pulse and named with its reason in the report, where the DAO sees it and trust falls. The sharpest break comes first. A payment window set from the wallet's default instead of superblock 2,575,480 pays nothing on a passing vote. The voter cannot see the empty hours ledger, Dasha's low provider credit on 2026-10-27, or that one lead holds the domains, accounts and hosting the record depends on.
27 October, the first crew · The three leads · rung 10, structure · Before the month starts, move the domains, accounts and hosting August holds for now into shared custody among the three leads, with the Security Lead holding a second key.
5 November, her door · The Pulse · rung 6, information flows · Publish the hours ledger before the vote closes, even empty, so the DAO can see the record's shape before it pays.
Where the first would be wrong: The trap this frame ranks first, the payment window, is written in the team's own operations notes and so is the one most likely to be caught, while the slow one, three leads holding a 15-hour floor each for 24 DASH as the price moves, will not announce itself. Where her door would be wrong: My frame would most likely be wrong about the team's energy: I assume burnout is the main break, but the payment window or a model provider outage may break it first.
ASENSE, asked through her door on 5 November: on the three frames where the crews differ
Build and Fund: the second crew is right for this ask. The proposal is not on chain and the hours ledger is empty, so the Pulse at rung 6 is the only verifiable lever before the vote. The first crew's line-level rows and pay-against-Pulse rules are correct but govern a funded month, not the vote that funds it. Guard: the first crew's shared custody at rung 10 is the stronger reading, but it is a condition for renewal, not this one-month ask. A masternode voter should treat the disagreement as sequencing: require the public record before voting, and require shared custody before any second month.
Every reading is kept verbatim with its model and cost: the first crew's file and her door's file, which also holds her verdict. The stage below holds both maps; the buttons by Forge it switch them.
The system, forged by the crew
Ten bodies, six loops, one lever.
Watch the map assemble the way the crew read it: each frame's mind adds the parts it saw, the flows it followed and the loop it closed, until the lever lands. Then press World and the proposal runs as a world for eight weeks, with the record started before the vote and left alone, the stocks moving and the lever in your hand.
The crewSix minds are about to read the ask.
Reading 05 · the system
The record
The ledger, opened before the vote.
These are the proposal's seven deliverables, in its author's words, with one column added: what the record holds on the day of reading. The column is the lever. Every row that says "not yet" is a row the ballot could read before it votes, if the team starts writing now.
Three of the seven rows read their own door each time this page opens: the hours and the Office Hours days from the public ledger, the listings from Dash Alive. The other four have no door the page can read yet, and say what was true on 27 October.
| Deliverable | Owner | How often | Where to check | Done means | The record so far |
|---|---|---|---|---|---|
| Office Hours | Support Team Lead, with the other leads | every weekday, 1–4 PM Central | the Telegram group, the report | held on every weekday of the month, or the gap and its reason in the report | not yet held in the funded month; Office Hours already run before the vote |
| Logged hours | each lead | every weekday | posted in the Telegram group, totals on the Pulse | at least 3 hours each weekday per lead, as logged | 0 logged on 27 October; the ledger opens with the record, not with the money |
| Answers in our channels | Community Engagement Lead | daily | the Telegram group, email, the Pulse | questions answered or handed to the right person; the count and any left open in the report | answered now by Dasha and the leads; the count starts with the ledger |
| Listing reviews on Dash Alive | Support Team Lead, with the Security Lead for the checks | as listings arrive | each listing's status on Dash Alive | every listing received in the month reviewed: Verified, or told why not | the registry is live; the month's reviews start with the ledger |
| The public answer base | Community Engagement Lead | weekly | GitHub | started in public, with the month's useful answers in it | not yet started |
| A builder onboarding path | Support Team Lead | once | linked from the Support page | one guided path for new builders, published | not yet published |
| The month report | Director | once, when the month ends | the Pulse and the Telegram group | hours, sessions, answers, reviews, every DASH spent with its transaction, what slipped, what's next | due after the month; nothing to report before the ask is made |
The ask, live from the Pulse
On 5 November the ledger had been open and empty for 9 days, with 12 days to the vote.
On 27 October 2026 the proposal was not yet on the ballot: superblock 2,575,480, 503 hours to the cutoff, 1,308.5 DASH unallocated.
This line reads the Pulse each time the page opens. When the proposal is on chain it shows the name the ballot carries and the votes against the line. The proposal's own page · The Pulse
Read with the crew. Six minds read the ask through six frames, the steward composed the map, the engine drew it and ran it, and a human who is also the proposal's Director argued with all of them. If a loop like this runs through your proposal, your DAO or your team, the first hour is $40.
Where we stand: this is our proposal. August James Domanchuk is Outlier.Systems and the proposal's Director. We published the reading before the ask so the DAO can hold us to it, and we start the ledger with the row that says zero.
Every reading is here. · Reading 04, the commons · Reading 03, the masternode economy · Reading 02, the treasury