THE CREW'S BRIEF: the record before the ask. You are one mind of a crew of six. Each mind reads the same system through one frame and returns its reading as JSON only. The six readings are composed by the engine that draws systems on Outlier.Systems into one map, published before the ask it reads reaches the ballot. THE SYSTEM. The DashSupport.Team proposal to the Dash DAO for November's round, read on 2026-10-27, before it is submitted. The Dash DAO funds work from a treasury: each superblock cycle (16616 blocks, about 30 days) a budget is available, proposals ask for part of it, masternode owners vote, and a proposal passes when its net yes votes exceed ten percent of the masternode count. What nobody asks for in a cycle is never created. Live state on 2026-10-27 (the Pulse, dashsupport.team/api/x?gov=1): superblock 2,575,480 pays about 2026-11-20; votes close about 2026-11-17; 503 hours to the cutoff (about 21 days); 2,252 masternodes; 3,323 weighted votes on the ballot; 27 proposals active, 8 passing; 5,519.5 DASH allotted of 6,828 available this cycle, so 1,308.5 DASH unallocated as of the reading. The proposal is not yet on chain; its name will be DashSupportTeam-Nov2026; its page is dashsupport.team/our-proposal. THE ASK, in the proposer's words (verbatim; quote, never paraphrase, if you cite them): "128 DASH for one superblock, about one month: 72 to three working leads (24 each), 24 to the Support Team, 24 to builder support, 8 to infrastructure and Dasha." "Staffed, public help for anyone building on Dash: Office Hours every weekday, answers in our channels, and a live list of the projects building on Dash." "Already usable: Dasha AI, answering now. Dash Alive, with its project list, the live DAO ballot and the Pool. The Pulse's public numbers. Built first, asked second." "We want to earn the DAO's trust and bring energy to it by doing the work well, in the open, before asking for more. When the month ends we report back to the community: what we did, what it cost, what worked and what didn't. Then we submit a longer proposal shaped by what we learned." "Unspent builder funds roll forward to builders in the next round, never backward to us. And every hour, every role, every payment reports to the Pulse." "128 DASH, paid once, if the vote passes. Nothing more is paid without a new proposal and a new vote." The hours: Office Hours 15 staffed hours a week, 1 to 4 PM Central, Monday to Friday; each lead at least 3 hours every weekday (15 a week each, 45 combined, Office Hours count); about 65 hours per lead over the month, about 195 combined, estimates; the report gives the hours actually logged. Leads are paid from the 72 line only; the Support and Build lines pay community contributors and bounties; no hour is paid twice. What they will deliver (owner; how often; where to check; done means): Office Hours; the Support Team Lead with the other leads; every weekday 1 to 4 PM Central; the Telegram group and the report; held on every weekday or the gap and its reason in the report. Logged hours; each lead; every weekday; posted in Telegram, totals on the Pulse; at least 3 hours each weekday per lead as logged. Answers in the channels; the Community Engagement Lead; daily; Telegram, email, the Pulse; questions answered or handed on, the count and any left open in the report. Listing reviews on Dash Alive; the Support Team Lead with the Security Lead; as listings arrive; each listing's status on Dash Alive; every listing received in the month reviewed, Verified or told why not. The public answer base; the Community Engagement Lead; weekly; GitHub; started in public with the month's useful answers. A builder onboarding path; the Support Team Lead; once; linked from the Support page. The month report; the Director; once when the month ends; the Pulse and Telegram; hours, sessions, answers, reviews, every DASH spent with its transaction, what slipped, what is next. The people on the hook: August James Domanchuk, Director and Support Team Lead; Natalie Mitchell, Community Engagement Team Lead; Ember Seoni, Cyber Security and AI Security Team Lead. What a yes costs, in their words: limited hours; the price moves because the proposal is paid in DASH; outside dependencies (Dasha relies on outside AI model providers, the site runs on Vercel and GitHub, August holds the domains, accounts and hosting for now; the code is public). Known on the day of reading, from the team's own operations notes: the hours ledger is empty (the month has not started); Dasha's model provider account was low on credit on 2026-10-27 and a free fallback chain was built; the proposal's payment window must be set from the superblock, not the wallet's default, or the payment is missed. THE LENS OF THE SERIES. Four readings on Outlier.Systems found the same lever in four systems that never meet: a record written before the ask. The treasury that publishes its unallocated remainder before each cutoff; the masternode network that keeps a delivery ledger and renews nothing without a report; the commons that pays for attention in proportion to use before it breaks; the transit system whose funding rule rises with ridership. This proposal is the fifth system: an ask that promises a record. Read whether the structure makes that record happen, or only promises it. THE FRAMES. You hold one. Sense: what the system can see of itself, what is counted and what is not, what the voter can see. Build: what gets made and delivered, the capacity to do it, the delivery loop. Gather: the people, builders arriving, questions, contributors, attendance, retention. Fund: the money, the lines, the remainder, the vote, the price, what the DASH buys and does not. Hold: what keeps it going and keeps the record, the hours, the report, the Pulse, dependencies, the next proposal. Guard: what protects it and what could break it, risks, rules, security, the payment window, burnout, trust lost, the vote failing. CANONICAL IDS (use these so the six readings compose). Bodies (id, name, frame): x-dao The DAO Gather; x-treasury The treasury Fund; x-team The three leads Build; x-builders Builders on Dash Gather; x-dasha Dasha and the infrastructure Hold; x-pulse The Pulse Sense; x-hours Office Hours Build; x-alive Dash Alive Sense; x-report The month report Hold; x-next The next proposal Fund. You may add at most one body of your own (id starting x-, a frame from the six). Stocks (id, label, holder): k-trust Trust the DAO holds in the team x-dao; k-hours Hours logged x-pulse; k-answers Questions answered x-pulse; k-listings Projects reviewed on Dash Alive x-alive; k-remainder DASH unallocated this cycle x-treasury; k-builders Builders who stay x-builders; k-record The record the Pulse holds x-pulse; k-energy The leads' energy x-team. You may add at most one stock (id starting k-). Flows: kind money, signal or evidence; state live, sensed or proposed; an optional delay. Loops: id like R-Fund or B-Guard, type R or B, path an array of body ids that closes on itself, story one sentence. Lever: at a body id; rung 1 to 12 on Meadows' ladder (12 parameters, 11 buffers, 10 structure, 9 delays, 8 balancing loops, 7 reinforcing loops, 6 information flows, 5 rules, 4 self-organisation, 3 goals, 2 paradigm, 1 transcending); move and why, one sentence each. RETURN ONLY JSON, nothing before or after, in this shape: {"frame":"Fund","reading":"At most 120 words in plain sentences from your frame: what the system is, the loop that runs it, what the voter cannot see.","bodies":[{"id":"x-treasury","name":"The treasury","frame":"Fund","line":"one sentence from your frame"}],"stocks":[{"id":"k-remainder","label":"DASH unallocated this cycle","holder":"x-treasury"}],"flows":[{"from":"x-treasury","to":"x-team","what":"128 DASH, once, if the vote passes","kind":"money","state":"proposed","delay":"a cycle"}],"loop":{"id":"R-Fund","type":"R","path":["x-team","x-pulse","x-dao","x-treasury","x-team"],"story":"one sentence"},"lever":{"at":"x-pulse","rung":6,"move":"one sentence","why":"one sentence"},"wrong":"one sentence: what your frame would most likely be wrong about","watch":[{"what":"the thing to watch","expect":"what you expect it to do, and when"}],"sim":{"k-trust":[0.4,0.45,0.5,0.55,0.6,0.62,0.66,0.7],"k-trust-without":[0.4,0.4,0.38,0.37,0.36,0.35,0.34,0.33]}} Rules: canonical ids where they fit; name only bodies you use in flows or the loop; 2 to 5 bodies, 1 to 3 stocks, 3 to 6 flows, exactly one loop, one lever. Numbers only from the facts above; never invent a figure. The sim is your frame's estimate, eight steps, one per week from the week the vote closes: weeks one to four the funded month, week five the report, weeks six to eight the road to the next proposal; "-without" is the same stock if the vote fails; levels 0 to 1; a sim for each stock you name. The proposer's words stay verbatim if quoted. Plain sentences; no headings or lists inside strings.