Every task in plain words: a title, what stands today, what comes next, one of five status words; the record behind each row opens under it. What's needed from Omar: 26 questions ↓
One question per decision, with why it matters and what your answer unlocks. Answers save on this device; an answer reaches Makki only when you copy it and paste it into the line yourself.
Each saved version of an answer carries one of four states. Saved on this device: on this device only, until you hand it over. Copied — paste and send to Makki: after Copy all answers; until the office records a receipt for that exact version the page says: Makki has not confirmed receipt of this version. Received by Makki: only when a receipt for that version is on record. Applied: only when a dated decision names it. Editing after a receipt starts a new, unsent version; the received one stays in the history. Nothing here sends anything to anyone.
About $10–20 a month. It unlocks the whole text line: a labourer verifies his day and the safety talk by text with no login, the texted link opens in a plain browser with no account, failed texts are caught, and the crew's week goes to each man's phone. Buying the number and switching the line on are two separate clicks here: buying it sends nothing, and nothing goes out until the second one.
What it unlocks: Your answer moves 9 rows: Worker verification without full portal use; SMS failure detection and recovery and 7 more.
The one decision: Whether Makki buys the texting number, about $10–20 a month, and separately whether to activate the labourer text line: buying the number does not activate it, and that is a second decision.
Why only you can answer it: The texting number is a monthly cost and the switch that lets the app send texts; both are his to say yes to, and no dated word on this line names a day, a number or who pays.
Open: 9 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Buying the texting number is money and a go on sending; no dated decision on this line names a day or who pays, so the rows still wait on your word.
Trace: O2 — Omar 2026-10-03 00:31 UTC "Yes they get outbound lines but thats a later thing" (vault/topics/people/Omar.md): yes in principle, no day, no number; the canonical rows still read waiting on Omar (v2.4, 2026-10-31)
The question as recorded: Do we buy the texting number and switch on the labourer text line?
Reworded from the earlier question 1 (“Do we buy the texting number and switch on the labourer text line?”), one decision per question, in plain words · source: main BUILDER DELTA 2026-11-07T18:20Z carrying Omar 18:15Z Telegram 2186 (hive/EXECUTION_LOG.md); pin v2.1.0 (hive/checks/2026-11-07_requirements-tasks-b3.md, 2026-11-07) — the text is unchanged; its rows moved: O2 (merged into GL-067 in the tracker's archive) leaves the list by the archive rule and is wanted through its survivor, which sits here
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
These four rows are the two daily crew texts themselves. The morning line-up is the text that goes out before work, and the safety-talk sign-off a man signs on his own phone is the part of it he answers; the end-of-day confirm is his hours at the end of the shift. Each man's hours for the week going to his phone is a different send and is asked on its own question, not here. Every other automatic message is asked on its own question below.
What it unlocks: Your answer moves 4 rows: The labourer text line — a labourer who never logs in at all: the…; Each employee sent his own approval by text: his time and hours for… and 2 more.
The one decision: Whether the app itself sends the two daily crew texts once the owner has OK'd their wording; every other automatic message stays off until it is asked about on its own row.
Why only you can answer it: Every automatic send from the app is held by the no-send rule until Omar says which sends are allowed and who signs the wording; nobody else on this line can lift it.
Open: 4 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Every automatic send from the app is held by the no-send rule until you say which sends are allowed and who signs the wording off; no dated decision lifts it, and the rows under this question are the morning line-up with its safety-talk sign-off and the end-of-day hours confirm alone.
Trace: RULE #1 (AGENTS.md, standing since 2026-09-10): nothing sends without Omar's explicit OK; the canonical rows read waiting on Omar (v2.4, 2026-10-31)
The question as recorded: May the app send the two daily crew texts — the morning line-up and the end-of-day report — in the wordings the owner OKs, with every other automatic message staying off?
Reworded from the earlier question 2 (“May the app send messages on its own — crew broadcasts, each man's week to his phone, form alerts and the email digest?”), one decision per question, in plain words · source: main BUILDER DELTA 2026-11-07T18:20Z carrying Omar 18:15Z Telegram 2186 (hive/EXECUTION_LOG.md); pin v2.1.0 (hive/checks/2026-11-07_requirements-tasks-b3.md, 2026-11-07) — the text is unchanged; its rows moved: V16 (the crew broadcast) now reads its canonical row GL-022 by the row's own alias line instead of V16·codex by a numeric suffix, and lists here with it; Omar's independent live review of the All Tasks page, 2026-11-07 22:13 UTC Telegram 2233, carried by main's Builder order 2026-11-07T23:10Z (hive/EXECUTION_LOG.md); pin v2.3.0 (hive/checks/2026-11-07_requirements-tasks-b3.md, 2026-11-07) (bounded to the two daily crew texts; no blanket send consent)
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
These rows are specified or half-made and silent: every automatic send is held until you say which send is allowed. Answering this switches nothing on — each send you name still needs its wording OK'd and its switch flipped by the build. The two daily crew texts are asked on their own question above; the proposal-for-signature send is asked with the proposals question, and the certificate email with the certificates question.
What it unlocks: Your answer moves 16 rows: Project exception notifications; Schedule messaging and 14 more.
The one decision: Which other automatic messages the app may send: none, or only the ones you name, each with the event that fires it, the channel, who it goes to and who OKs the wording.
Each send this answer could permit, one at a time — the event, the channel, who receives it and who reviews the wording:
Why only you can answer it: Every automatic send from the app is held by the no-send rule until Omar says which sends are allowed and who signs the wording off; nobody else on this line can lift it.
Open: 16 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Every automatic send from the app is held by the no-send rule until Omar says which sends are allowed and who signs the wording off; no dated decision lifts it for these rows, and the two-daily-texts question does not cover them. Answering this switches nothing on by itself.
Trace: the no-send rule standing since Omar 2026-09-10 19:17 UTC; the canonical rows on this plan card read waiting on Omar or on both (v2.4, 2026-10-31); split out of the two-daily-texts question by main 2026-11-08T03:26Z carrying Omar 03:24Z
The question as recorded: Which of the app's other automatic messages may it send at all — crew broadcasts, each man's week to his phone, form alerts, the notification digest?
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Decides whose account the app runs in, what address the crew types, and where the real data, the database and the backups will sit. The owner's own account is the cleaner answer; a domain is $15–20 a year if Makki does not own one. The backup, capacity, domain and recovery rows are not held behind this answer — the hive builds them on demo data either way.
What it unlocks: Your answer moves 8 rows: Back up and export business data; Backups, restore and usable exports and 6 more.
The one decision: Which account hosts the app from the next publish: the owner's own at a Makki address, or EazyLife's for now. Where a second copy is kept is a separate question this answer does not decide.
Why only you can answer it: Whose account the app runs in, what address the crew types and where the real data sits are money and ownership choices; he set three requirements and named no provider, and his later words keep hosting his.
Open: 8 rows under this answer; the backup, capacity, domain and recovery rows are not held behind this answer and the hive builds them on demo data.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Whose account, which address and where the data sits are money and ownership choices; your 2026-10-03 requirements (a secure place, room to grow, a duplicate) name no provider.
Trace: O6 — Omar 2026-10-03 00:31 UTC, vault/topics/decisions/a secure place, room to grow, and a duplicate.md: three requirements, no provider named; canonical rows waiting on Omar (v2.4, 2026-10-31)
The question as recorded: Hosting — does the app run in the owner's own account at a Makki address, or in EazyLife's account for now?
Reworded from the earlier question 3 (“Hosting: the owner's own Cloudflare account or EazyLife's, a Makki address, and where the database and backups live?”), one decision per question, in plain words · source: Omar 2026-11-07 17:06 UTC Telegram 2174 (one decision per question, plain words, the recorded authorizations applied); main BUILDER ORDER 2026-11-07T17:40Z (hive/EXECUTION_LOG.md)
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
You open it and say; the row has waited on that one word since it went live.
What it unlocks: Your answer moves 1 row: Forms is live — good / bad / change; he opens it and says.
The one decision: Whether the Forms page as it stands today is good as it is, needs a change, or goes back for rework.
Forms — the site lead's Forms page in the app (sign in as the site lead) — open it, then answer here.
Why only you can answer it: Good, bad or change on a live screen is his review word alone; the row has waited on that one word since it went live and no dated word names it as reviewed.
Open: 1 row waits on this one answer; nothing moves on it until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Forms is live and waits on your review word alone; no dated word on this line names it as reviewed.
Trace: GL-069 — GO_LIVE.md row, waiting on Omar since 2026-09; canonical v2.4 (2026-10-31) waiting on Omar
The question as recorded: Forms is live — good, bad or change?
Split from the earlier question 4 (“Your open reviews — Forms, the Tickets pass, the Team page's demo email, the two silent jobs, the login slide — good, bad or change? And do we add the owner to this line?”), one decision per question; the earlier combined answer, if you gave one, is carried into this question's history.
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Live since 17 September and waiting on your word.
What it unlocks: Your answer moves 1 row: Tickets write · earlier design and phone passes — good / bad /….
The one decision: Whether the Tickets screens as they stand today are good as they are, need a change, or go back for rework.
Tickets — People → Tickets in the app (the owner's login), on desktop and on a phone — open it, then answer here.
Why only you can answer it: Good, bad or change on the live Tickets screens is his review word alone; nothing dated on this line says they were reviewed.
Open: 1 row waits on this one answer; nothing moves on it until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: The Tickets screens have been live since 2026-09-17 awaiting your word; no dated word names them as reviewed.
Trace: GL-074 — live since 2026-09-17 (GO_LIVE.md); canonical v2.4 (2026-10-31) waiting on Omar
The question as recorded: The Tickets screens — the ticket records, the earlier design and the phone layout — good, bad or change?
Reworded from the earlier question 5 (“The Tickets pass — the write pass, the earlier design and the phone passes — good, bad or change?”), one decision per question, in plain words · source: Omar's independent live review of the All Tasks page, 2026-11-07 22:13 UTC Telegram 2233, carried by main's Builder order 2026-11-07T23:10Z (hive/EXECUTION_LOG.md); pin v2.3.0 (hive/checks/2026-11-07_requirements-tasks-b3.md, 2026-11-07) (the artifact named in plain words; no test-history words)
Split from the earlier question 4 (“Your open reviews — Forms, the Tickets pass, the Team page's demo email, the two silent jobs, the login slide — good, bad or change? And do we add the owner to this line?”), one decision per question; the earlier combined answer, if you gave one, is carried into this question's history.
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
One word on a screen you have seen.
What it unlocks: Your answer moves 1 row: The Team page demo login prints an email address on screen — cut or….
The one decision: Whether the Team page's demo login keeps printing an email address on screen, or that line is cut.
Team & Access in the app (the owner's login) — the demo login line that prints an email address — open it, then answer here.
Why only you can answer it: Cut or leave is a one-word call on a screen he has seen; it is a choice about what the client sees, not a repair, and nothing dated settles it.
Open: 1 row waits on this one answer; nothing moves on it until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Cut or leave is a one-word call on a screen you have seen; nothing dated settles it.
Trace: GL-071 — GO_LIVE.md; canonical v2.4 (2026-10-31) waiting on Omar
The question as recorded: The Team page's demo login prints an email address on screen — cut it or leave it?
Split from the earlier question 4 (“Your open reviews — Forms, the Tickets pass, the Team page's demo email, the two silent jobs, the login slide — good, bad or change? And do we add the owner to this line?”), one decision per question; the earlier combined answer, if you gave one, is carried into this question's history.
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
A design call flagged as a decision, not a correction; one word closes it.
What it unlocks: Your answer moves 1 row: Estimator + bookkeeper on one login slide · 3 master-list rows….
The one decision: Whether the login slide keeps the estimator and the bookkeeper together, or each of them gets a slide of its own.
The login slide in the deck — open it, then answer here.
Why only you can answer it: One slide for both or a slide each is a design call he was asked and did not answer; the office made the one-slide choice on its own and said so, and his word is still the one that closes it.
Open: 1 row waits on this one answer; nothing moves on it until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: The one-slide-or-two call was flagged as a decision, not a correction, and the canonical row still reads waiting on Omar.
Trace: GL-075 — the login slide alone stays the question; the bid-versus-actual tab is GL-043, authorised 2026-10-06 (implementation now, on your runtime.md) and routed by its state; the three master-list rows V45, V17 and V132/V84 route by their own canonical states (canonical v2.4, 2026-10-31); GO_LIVE.md
The question as recorded: The login slide — keep the estimator and the bookkeeper on one slide, or give each a slide of its own?
Reworded from the earlier question 8 (“One login slide for the estimator and the bookkeeper, the three master-list rows flagged as decisions, and the bid-versus-actual tab — decide each?”), one decision per question, in plain words · source: Omar 2026-11-07 17:06 UTC Telegram 2174 (one decision per question, plain words, the recorded authorizations applied); main BUILDER ORDER 2026-11-07T17:40Z (hive/EXECUTION_LOG.md)
Split from the earlier question 4 (“Your open reviews — Forms, the Tickets pass, the Team page's demo email, the two silent jobs, the login slide — good, bad or change? And do we add the owner to this line?”), one decision per question; the earlier combined answer, if you gave one, is carried into this question's history.
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
You asked twice why it posts; one word changes it.
What it unlocks: Your answer moves 1 row: The nightly report posts here; twice he's asked why — say "quiet"….
The one decision: Whether the night report files itself silently instead of posting on the line.
The board's feed, where the nightly report lands — open it, then answer here.
Why only you can answer it: The nightly report posts on his line because he has not said quiet; he asked three times why it arrives and the offer to file it silently is still his to take or leave.
Open: 1 row waits on this one answer; nothing moves on it until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: You asked twice why the nightly report posts; saying quiet would file it silently, and the word is still yours.
Trace: GL-070 — GO_LIVE.md; canonical v2.4 (2026-10-31) waiting on Omar
The question as recorded: The nightly report posts on the line — say 'quiet' and it files silently instead?
Split from the earlier question 4 (“Your open reviews — Forms, the Tickets pass, the Team page's demo email, the two silent jobs, the login slide — good, bad or change? And do we add the owner to this line?”), one decision per question; the earlier combined answer, if you gave one, is carried into this question's history.
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
The licensed catalogue is money and an outside service, so that part is yours. The training matrix and the onboarding material were released from your queue on 4 October 2026 and are not held by this answer — the hive builds them on demo data either way; only the licensed course content waits on your word.
What it unlocks: Your answer moves 2 rows: Licensed training catalogue option; Licensed training catalogue decision and integration.
The one decision: Whether Makki pays for a licensed training catalogue, or the app ships with Makki's own training material only.
Why only you can answer it: A licensed training catalogue is a paid outside service, and no new paid service starts without his word; the training rows take one shape with it and another without, so they wait on that one choice.
Open: 2 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: The licensed training catalogue is a paid service and no new paid service starts without your word; only the licensed course content takes its shape from that one choice.
Trace: O7 — The owner's ask on the call (profile/Fieldflo_Competitor_Call_2026-09-08.md); M-CAT a paid catalogue, no new paid services (vault/topics/decisions/implementation now, on your runtime.md, 2026-10-06); canonical rows waiting on Omar (v2.4, 2026-10-31)
The question as recorded: Training on the phone — pay for a licensed training catalogue, or go without one?
Reworded from the earlier question 12 (“Training on the phone — build the training matrix, onboarding materials and the manager orientation video, and is a licensed training catalogue in or out?”), one decision per question, in plain words · source: Omar 2026-11-07 17:06 UTC Telegram 2174 (one decision per question, plain words, the recorded authorizations applied); main BUILDER ORDER 2026-11-07T17:40Z (hive/EXECUTION_LOG.md)
Reworded again to the one real decision (the build parts are the hive's — a repair you can do is not a decision): earlier wording “Training on the phone — do we build the training matrix, the onboarding and the orientation video with a paid training catalogue, or without one?” · the build parts are the hive's; the paid catalogue is the decision · source: main BUILDER DELTA 2026-11-07T18:20Z carrying Omar 18:15Z Telegram 2186 (hive/EXECUTION_LOG.md); pin v2.1.0 (hive/checks/2026-11-07_requirements-tasks-b3.md, 2026-11-07)
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Today the app is a browser-only prototype: no server, no database, and no server-enforced authentication — the logins are a browser pretence. Starting the server side is build time plus a running bill: about $25–40 a month, hosted on one small managed instance where the database and the audit trail would run. These rows are that work plus a security and data-handling review.
What it unlocks: Your answer moves 8 rows: Authorization enforced throughout the system; Audit changes and corrections and 6 more.
The one decision: Whether the hive starts the server side now for the authorised demo build, or leaves it for a production launch, whose monthly cost is part of this answer.
Why only you can answer it: A server with enforced logins, an audit trail and sync is hosting cost and a real-data step; his authorisation covers demo fixes only and says in so many words that a server is still his word.
Open: 8 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Starting the server side is a build-and-cost decision outside the demo rails: server auth and shared-data design are prepared as documents, not deployed, until you say start.
Trace: vault/topics/decisions/implementation now, on your runtime.md (2026-10-06): server auth and shared-data design prepared as documents, not deployed; canonical rows waiting on Omar (v2.4, 2026-10-31)
The question as recorded: Do we start the server side — logins enforced on a server, an audit trail, sync and conflict recovery — or stay browser-only until the owner's data is in?
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Launch readiness is the second finish line, and one name signs the cut-over to the real business. Who owns support and who watches the monitoring are separate questions and are not settled by this one.
What it unlocks: Your answer moves 4 rows: Controlled cutover and launch approval; Monitoring, incident response and status and 2 more.
The one decision: Who signs the one go-live approval for the cut-over to the real business: Omar, the owner, or both.
Why only you can answer it: Who approves the cut-over to the real business is the second finish line; it is an approval, not a build, and the hive cannot give it to itself.
Open: 4 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Cut-over approval, support ownership and monitoring are the second finish line and are not the hive's to decide.
Trace: vault/topics/decisions/two finish lines.md (2026-10-10); canonical rows waiting on Omar (v2.4, 2026-10-31)
The question as recorded: Pilot and launch — who approves the cut-over to the real business?
Reworded from the earlier question 14 (“Pilot and launch — who approves the cut-over, who owns support, and what monitoring do we stand up?”), one decision per question, in plain words · source: Omar 2026-11-07 17:06 UTC Telegram 2174 (one decision per question, plain words, the recorded authorizations applied); main BUILDER ORDER 2026-11-07T17:40Z (hive/EXECUTION_LOG.md)
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Until your word, every figure carries the demo header. It also waits on the owner's QuickBooks login — a login, not an integration — and on the migration of his workbook, which is not specified yet.
What it unlocks: Your answer moves 1 row: Demo data → real data — Omar's word that the real data is connected….
The one decision: What must be true before the demo header comes off: the evidence that the owner's own records are in the app and reconcile.
Why only you can answer it: Only his word connects the real data and takes the demo header off; until then every figure is demo by the rails, and that word has not been given.
Open: 1 row waits on this one answer; nothing moves on it until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Only your word connects the real data and takes the demo header off; it also waits on the owner's QuickBooks login and a workbook migration that is not specified yet.
Trace: GL-044 — rail 7 (every figure is demo until Omar says the real data is connected); QuickBooks "later, just make sure its ready to import" (Omar 2026-10-03 00:31 UTC, vault/topics/people/Omar.md); canonical row waiting on Omar (v2.4, 2026-10-31)
The question as recorded: Real data — when do you say the real data is connected and the demo header comes off?
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Reading a mailbox was never ruled on; the no-send rule covers sending only. These rows wait on that word and on the owner's logins.
What it unlocks: Your answer moves 4 rows: Connect the operating tools; Link calendar events to jobs and 2 more.
The one decision: Whether the app may read the owner's email, calendar and workbook, one at a time and each only after he grants that one access, reading only and never sending.
Why only you can answer it: Reading the owner's mailbox, calendar or workbook was never ruled on — the no-send rule covers sending only — and his authorisation says a mailbox read is not approved by it; that leaves the word his.
Open: 4 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Reading a mailbox, a calendar or the workbook was never ruled on; the no-send rule covers sending only, and the owner's logins are needed.
Trace: RULE #1 is sending — reading a mailbox was never ruled on (vault/topics/projects/Fieldflo.md, 2026-10); canonical rows waiting on Omar (v2.4, 2026-10-31)
The question as recorded: Do we connect the owner's email, calendar and workbook to the app — each one only after he grants that one access?
Reworded from the earlier question 16 (“Do we connect the owner's email, calendar and workbook to the app?”), one decision per question, in plain words · source: Omar's independent live review of the All Tasks page, 2026-11-07 22:13 UTC Telegram 2233, carried by main's Builder order 2026-11-07T23:10Z (hive/EXECUTION_LOG.md); pin v2.3.0 (hive/checks/2026-11-07_requirements-tasks-b3.md, 2026-11-07) (bounded: each connection only after the owner grants that one access; reading, never sending)
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Today it only answers from the data. Letting it act needs your rule on which records it may change; the office reviews every change before it lands, and the office is the reviewer named here.
What it unlocks: Your answer moves 4 rows: Keep business records as the authoritative data; Monitor assistant quality and usage and 2 more.
The one decision: Which record kinds the text assistant may change when told to — the schedule, a crew, a shift or a timesheet — always with a review step before the change lands.
Why only you can answer it: Letting the assistant change records is a rule on what it may touch and who reviews it; no decision page on this line sets that rule, so it is his to set.
Open: 4 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Letting the assistant change records needs your rule on what it may change, who reviews it and how its quality is watched; no dated word settles it.
Trace: canonical rows waiting on Omar (v2.4, 2026-10-31); no decision page on this line names the assistant's write rights
The question as recorded: The assistant by text — may it change records when told to ('bump Crew B to Thursday'), with a review step before the change lands?
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
The owner has not answered the GPS question; until a rule is set nothing records a man's location. One choice: collect it or not, and for whom.
What it unlocks: Your answer moves 2 rows: Location verification request; GPS clock-in / photo clock-out (FlōTime) — location-verified start….
The one decision: Whether the app records where a man clocks in from, and if so who may see it: the owner alone, the owner and his managers, or nobody.
Why only you can answer it: Whether the app records where a man clocks in from, and who may see it, is a privacy rule for the company; the owner has not answered the GPS question and no dated word on this line sets the rule.
Open: 2 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: GPS on clock-in needs one rule on whether it is collected and who sees it; the owner has not answered the GPS question and no dated word on this line sets the rule.
Trace: canonical rows waiting on Omar or on both (v2.4, 2026-10-31); the owner's GPS answer pending since 2026-10-03; split from the combined privacy question on 2026-11-07 (Omar's live review, Telegram 2233)
The question as recorded: Clock-in location — do we record where a man clocks in from and who gets to see it?
Split from the earlier question 19 (“GPS on clock-in and HR privacy — do we show where a man clocks in from, and who may open HR records?”), one decision per question; the earlier combined answer, if you gave one, is carried into this question's history.
Dated sources showing no later decision:
The HR file holds a man's employee number, pay group and union; one rule says who may open it. The write-ups are asked below, separately: this question does not cover them.
What it unlocks: Your answer moves 2 rows: Keep location and HR access limited; Location and HR privacy controls.
The one decision: Who may open a man's HR file: the owner alone, or the owner and his managers.
Why only you can answer it: Who may open a man's HR file is a privacy rule for the company, a choice about what people see and not a repair; no dated word on this line sets it.
Open: 2 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Who may open a man's HR records needs a rule from you and the owner; no dated word on this line sets it.
Trace: canonical rows waiting on Omar or on both (v2.4, 2026-10-31); split from the combined privacy question on 2026-11-07 (Omar's live review, Telegram 2233)
The question as recorded: HR records — who may open a man's HR file: the owner alone, or the owner and his managers?
Split from the earlier question 19 (“GPS on clock-in and HR privacy — do we show where a man clocks in from, and who may open HR records?”), one decision per question; the earlier combined answer, if you gave one, is carried into this question's history.
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
The hazard sheet already shows the site weather with how fresh it is, on seeded demo numbers, and the outside feed is off. The one open choice is whether the app may call an outside feed for real numbers at all, and that is yours. The proposal below names the service, what it costs, every field that would leave the box and the one setting that would switch it on; its suitability, its cost and that data disclosure are checked and confirmed before any call is made. Picking the technical service is the build's work.
What it unlocks: Your answer moves 1 row: Live job weather with visible freshness.
The one decision: Whether the app may call an outside weather feed at all: yes to the free feed set out in the proposal below, no, or not yet. The build picks the provider.
Why only you can answer it: A live weather feed is an outside service the app would call, and whether it may call anything outside at all is his word; no dated decision on record gives it.
Open: 1 row under this answer; the panel on the hazard sheet is build work on seeded numbers and is not held behind it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Whether the app may call anything outside at all is your word, and no dated decision gives it. The proposal below is prepared, not applied: nothing is activated and no call is made until your word gives it; the technical pick is the build's, and the broader standing rule that was carried here has no dated decision behind it.
Trace: O-WEATHER — no new paid services (vault/topics/decisions/implementation now, on your runtime.md, 2026-10-06); canonical v2.4 (2026-10-31) waiting on Omar; V41·codex and M-ACK decided 2026-10-06 (implementation now)
The question as recorded: Live weather on the job site — may the app call an outside weather feed at all?
Reworded from the earlier question 20 (“JHA — live weather on the job, a daily JHA reused with a fresh review, and auditor acknowledgements: build on demo data?”), one decision per question, in plain words · source: Omar 2026-11-07 17:06 UTC Telegram 2174 (one decision per question, plain words, the recorded authorizations applied); main BUILDER ORDER 2026-11-07T17:40Z (hive/EXECUTION_LOG.md); Omar's independent live review of the All Tasks page, 2026-11-07 22:13 UTC Telegram 2233, carried by main's Builder order 2026-11-07T23:10Z (hive/EXECUTION_LOG.md); pin v2.3.0 (hive/checks/2026-11-07_requirements-tasks-b3.md, 2026-11-07) (the why no longer derives the free feed from the no-paid-services rule)
Reworded again to the one real decision (the build parts are the hive's — a repair you can do is not a decision): earlier wording “Live weather on the job site — which weather feed may the app use?” · The earlier wording asked you to pick the feed and carried the standing rule “Your word naming the feed, free or paid; the app calls no outside service until then.” Naming an outside weather service is yours on a dated source of 2026-10-04; the blanket part of that rule — that the app may call nothing outside at all — has no dated decision behind it, and the technical pick is the build's work, not yours. Kept here as history, not rewritten away. · source: Codex review ruling 2026-11-08T04:12Z, under Omar's standing instructions, relayed by main, and main's ORDER 2026-11-08T03:26Z carrying Omar 2026-11-08 03:24 UTC (hive/EXECUTION_LOG.md); tasks-correction v1.0.0, 2026-11-08. The ruling authorised the source reconciliation and the preparation of a proposal; it approved no feed and answered no question.
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
The seat is drafted on demo quotes. Whether a number the AI makes may ever be shown to a customer is your rule to set. The optional takeoff experiment is its own row and is not settled by this question; the owner's past quotes were put off to later.
What it unlocks: Your answer moves 3 rows: Optional takeoff and estimating exploration; Optional drawing takeoff and estimate experiment and 1 more.
The one decision: Whether a number the AI takeoff makes may ever reach a customer, or stays internal to the office and the demo build until you say otherwise.
Why only you can answer it: Whether an AI-made estimate is ever put in front of a customer is a rule about the business's own quotes; it is his to set, and the owner's past quotes were put off to later by his own word.
Open: 3 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Whether an AI estimate is ever shown to a customer, and whether the optional takeoff experiment is in scope, are your calls; the build itself is the hive's once you say.
Trace: canonical rows waiting on Omar (v2.4, 2026-10-31); the owner's past quotes were put off "later" (Omar 2026-10-03 00:31 UTC, vault/topics/people/Omar.md)
The question as recorded: The AI takeoff and estimate — may a number it makes ever go in front of a customer?
Reworded from the earlier question 21 (“The Estimator and AI takeoff — build it on the owner's past quotes, or wait for them?”), one decision per question, in plain words · source: main BUILDER DELTA 2026-11-07T18:20Z carrying Omar 18:15Z Telegram 2186 (hive/EXECUTION_LOG.md); pin v2.1.0 (hive/checks/2026-11-07_requirements-tasks-b3.md, 2026-11-07)
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Installing the app on phones and desktops with safe updates is build time and ships either way. A store listing costs money — about $25 a year for a developer account in someone's name, and a review on each release — so that part is your word.
What it unlocks: Your answer moves 1 row: Optional public app-store distribution.
The one decision: Whether Makki pays for an app-store listing and the developer account in someone's name, or the app stays on its install link.
Why only you can answer it: A store listing costs money and needs a developer account in someone's name; no new paid service starts without his word, while the install and update work ships one way or the other on that choice.
Open: 1 row waits on this one answer; nothing moves on it until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: An app-store listing costs money and time and needs an account in someone's name; the install and update rows ship one way or the other on that choice.
Trace: O-STORE — no new paid services (vault/topics/decisions/implementation now, on your runtime.md, 2026-10-06); canonical rows waiting on Omar (v2.4, 2026-10-31)
The question as recorded: An app-store listing for the app — pay for one, or stay with the install link?
Reworded from the earlier question 22 (“Install — the app on phones and desktop as an installable app with safe updates and rollback; and an app-store listing, or not?”), one decision per question, in plain words · source: main BUILDER DELTA 2026-11-07T18:20Z carrying Omar 18:15Z Telegram 2186 (hive/EXECUTION_LOG.md); pin v2.1.0 (hive/checks/2026-11-07_requirements-tasks-b3.md, 2026-11-07)
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Sending a proposal out for signature is a send, held until you allow it. Turning an accepted quote into a job is build work: it is not held by this answer and the hive builds it on demo data either way.
What it unlocks: Your answer moves 2 rows: E-signature on proposals — send-for-signature directly from the…; Auto-send — SMS, email, e-sign ("Ready SMS", Auto-Send….
The one decision: Whether the app may send a proposal out for signature at all — only the send is asked here; turning an accepted quote into a job is build work and is not settled by this answer.
Why only you can answer it: Sending a proposal out for signature is a send; the no-send rule holds every send until he allows it by name.
Open: 2 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Sending a proposal out for signature is a send, held by RULE #1 until you allow it; the build work on the same subject is not held by it.
Trace: R03 — RULE #1 (sending); canonical rows waiting on Omar (v2.4, 2026-10-31)
The question as recorded: Proposals — may the app send a proposal for e-signature straight from the app?
Reworded from the earlier question 23 (“Proposals — e-signature straight from the app, and accepted quotes turning into jobs?”), one decision per question, in plain words · source: Omar 2026-11-07 17:06 UTC Telegram 2174 (one decision per question, plain words, the recorded authorizations applied); main BUILDER ORDER 2026-11-07T17:40Z (hive/EXECUTION_LOG.md)
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Today the Collector drafts every invoice and the owner sends it himself. The drafting is built and running and is not held by this answer — drafting continues either way; only whether the app itself ever sends one is asked here.
What it unlocks: Your answer moves 2 rows: Offer conversational invoicing; Remove owner mediated invoicing handoffs.
The one decision: Whether the app ever sends an invoice itself after the owner's OK, or the owner sends every one himself.
Why only you can answer it: Whether the app may send an invoice itself changes who sends; today the owner sends every one and the no-send rule keeps it that way until his word.
Open: 2 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Whether the app may send invoices itself changes who sends (RULE #1); the Collector's drafting runs today and is not held by this answer.
Trace: RULE #1; vault/topics/decisions/the money reports live in the app.md (2026-10-10) — the Collector is a convenience, never the route; canonical rows waiting on Omar (v2.4, 2026-10-31)
The question as recorded: Invoicing — may the app send invoices itself, or does the owner keep sending every one?
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Recording use means recording something about each man, and the familiar workflow stays as it is either way. Who may see it: the owner and his managers, nobody else. Whether it identifies him: the record is per man, by name, so he can be asked about it. How long it is kept: 90 days, then deleted.
What it unlocks: Your answer moves 1 row: Make field adoption measurable.
The one decision: Exactly what the app may record about how each man uses it: which screens he opens and how many times per week, and nothing else.
Why only you can answer it: Recording how each man uses the app records something about each man; that is a rule about the crew's data and no dated word on this line gives it.
Open: 1 row waits on this one answer; nothing moves on it until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Measuring how the crew uses the app records something about each man; that needs your OK, and the workflow question is a yes or a no.
Trace: canonical rows waiting on Omar (v2.4, 2026-10-31); no decision page names adoption measurement
The question as recorded: Field adoption — may the app record how each man uses it, so the office can see what gets used?
Reworded from the earlier question 25 (“Field adoption — may the app measure how the crew uses it, and does the familiar workflow stay as it is?”), one decision per question, in plain words · source: Omar 2026-11-07 17:06 UTC Telegram 2174 (one decision per question, plain words, the recorded authorizations applied); main BUILDER ORDER 2026-11-07T17:40Z (hive/EXECUTION_LOG.md)
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Today the app refuses the add outright and names every missing ticket. The warning is not built and nothing is emailed — the office line is a demo note written on screen. Two different emails could be wanted: one about a blocked attempt, and one about an override somebody explicitly proposes. Your rule settles which, if either; the refusal itself stays as it is.
What it unlocks: Your answer moves 2 rows: Emailing the office about a refused add, or an explicitly proposed…; A man without the right certs: the add is refused, and the office is….
The one decision: Whether the refusal stays as it is, and whether the office is emailed — about a blocked attempt, about an explicitly proposed override, or not at all; the wording is OK'd before anything goes out.
Why only you can answer it: The warning is built; emailing the office is a send, and the no-send rule holds it until he sets the rule.
Open: 2 rows wait on this one answer; nothing moves on them until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: A message to the office is a send, held by the no-send rule until you set the rule; what the app does today is a refusal, not a warning, and the warning is not built.
Trace: V88 — RULE #1 (sending); canonical row waiting on Omar (v2.4, 2026-10-31)
The question as recorded: When a man without the right certificate is refused a job, does the office hear about it?
Reworded from the earlier question 27 (“A man added to a job without the right certs — warn the supervisor, and email the office if he is added anyway?”), one decision per question, in plain words · source: Omar 2026-11-07 17:06 UTC Telegram 2174 (one decision per question, plain words, the recorded authorizations applied); main BUILDER ORDER 2026-11-07T17:40Z (hive/EXECUTION_LOG.md)
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
The records sit on the man's page; the rule on who sees them is yours and the owner's.
What it unlocks: Your answer moves 1 row: Restricted disciplinary records.
The one decision: Who may open the restricted disciplinary records: the owner alone, or the owner and his managers. This is a narrower set than the HR file and is decided separately.
Why only you can answer it: Who may open restricted disciplinary records is an access rule for the company, his and the owner's to set; the rails keep owner-only records closed until a rule says otherwise.
Open: 1 row waits on this one answer; nothing moves on it until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: Who may open restricted disciplinary records is a rule for you and the owner.
Trace: M-DISC — canonical row waiting on Omar (v2.4, 2026-10-31)
The question as recorded: Restricted disciplinary records — who may open them?
Dated sources showing no later decision:
Optional. It is a second product and would come after the crew's app.
What it unlocks: Your answer moves 1 row: Optional customer self-service portal.
The one decision: Whether a customer self-service portal is in scope at all, or stays out until the crew's app is finished.
Why only you can answer it: A customer self-service portal is a second product; in or out is a scope decision only he makes.
Open: 1 row waits on this one answer; nothing moves on it until Omar gives it.Pick a choice or type an answer and save it; it stays on this device until you copy all answers into the line.
Open because: A customer self-service portal is a second product; in or out is a scope decision only you make.
Trace: O-CLIENT — canonical row waiting on Omar (v2.4, 2026-10-31)
The question as recorded: A customer self-service portal — in or out?
Dated sources showing no later decision:
Dated lines this question's own reading is read from:
Completed 243 / Not done 116 / Needs Omar 66 · Needs Ali 124 · Needs both 16 · Declined 1The tracker's 566 live canonical rows today, by the five words. Final review (a separate ruling on evidence, a detail and never a status): ruled 11 of 566.
Three queues, one queue each — exclusive: Omar 66 · the owner 124 · both 16; a row carries one owner field, so it sits in exactly one queue and the three never overlap. Counting the shared rows on both sides: Omar 82 (his own plus the shared), the owner 140 (his own plus the shared), shared 16.
Who the remaining work waits on: waiting on Omar 82 (66 his alone + 16 shared) · waiting on the owner 140 (124 his alone + 16 shared) · AI work remaining 195 of 436 — the AI-executable set against its own denominator, 95 Not done plus 100 waiting on an answer · Completed 243 — finished on demo data, the shared and input rows counted there too, never AI-only work · Tracker-wide Not done 116 — every live row that waits on nobody's word, counted over all 566 live rows and never the figure above.
The 124 tracker rows waiting on the owner alone — things only he can send, say or decide. Separate from Omar's questions and from the 16 rows that wait on both.
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: plat-install · the full record, with the title as recorded, is the tracker's row D07 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: plat-auth · the full record, with the title as recorded, is the tracker's row D12 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-quotes · the full record, with the title as recorded, is the tracker's row F04 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-time · the full record, with the title as recorded, is the tracker's row F10 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-payroll · the full record, with the title as recorded, is the tracker's row F12 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-cost · the full record, with the title as recorded, is the tracker's row F16 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-crm · the full record, with the title as recorded, is the tracker's row F42 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-quotes · the full record, with the title as recorded, is the tracker's row F43 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-jha · the full record, with the title as recorded, is the tracker's row F48 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row F57 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-payroll · the full record, with the title as recorded, is the tracker's row R12 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-money · the full record, with the title as recorded, is the tracker's row R14 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: gear-ware · the full record, with the title as recorded, is the tracker's row R16 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-est · the full record, with the title as recorded, is the tracker's row R17 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-est · the full record, with the title as recorded, is the tracker's row R18 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: office-connect · the full record, with the title as recorded, is the tracker's row R19 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-payroll · the full record, with the title as recorded, is the tracker's row R21 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-lang · the full record, with the title as recorded, is the tracker's row V03·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: mgmt-forms · the full record, with the title as recorded, is the tracker's row V10·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row V17·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-cutover · the full record, with the title as recorded, is the tracker's row V18·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-lib · the full record, with the title as recorded, is the tracker's row V31·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-lib · the full record, with the title as recorded, is the tracker's row V32·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: mgmt-projbook · the full record, with the title as recorded, is the tracker's row V33·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-quotes · the full record, with the title as recorded, is the tracker's row V34·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-startday · the full record, with the title as recorded, is the tracker's row V37·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-jha · the full record, with the title as recorded, is the tracker's row V42·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-contain · the full record, with the title as recorded, is the tracker's row V45·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-startday · the full record, with the title as recorded, is the tracker's row V46·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-payroll · the full record, with the title as recorded, is the tracker's row V52·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-payroll · the full record, with the title as recorded, is the tracker's row V53·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: plat-host · the full record, with the title as recorded, is the tracker's row V55·codex in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-cutover · the full record, with the title as recorded, is the tracker's row W01 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-cost · the full record, with the title as recorded, is the tracker's row W06 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-money · the full record, with the title as recorded, is the tracker's row W08 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: gear-ware · the full record, with the title as recorded, is the tracker's row W12 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-money · the full record, with the title as recorded, is the tracker's row W13 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-money · the full record, with the title as recorded, is the tracker's row W14 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-cutover · the full record, with the title as recorded, is the tracker's row W15 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: mgmt-projbook · the full record, with the title as recorded, is the tracker's row M-BOOK in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: office-company · the full record, with the title as recorded, is the tracker's row M-BRAND in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-contain · the full record, with the title as recorded, is the tracker's row M-CONT in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-crm · the full record, with the title as recorded, is the tracker's row M-CRM in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-startday · the full record, with the title as recorded, is the tracker's row M-DAY in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-est · the full record, with the title as recorded, is the tracker's row M-EST in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-people · the full record, with the title as recorded, is the tracker's row M-HR in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-lang · the full record, with the title as recorded, is the tracker's row M-LANG in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: gear-ware · the full record, with the title as recorded, is the tracker's row M-MAT in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-cutover · the full record, with the title as recorded, is the tracker's row M-MIG in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: plat-install · the full record, with the title as recorded, is the tracker's row M-OFF in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-payroll · the full record, with the title as recorded, is the tracker's row M-PAY in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row M-QBO in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-quotes · the full record, with the title as recorded, is the tracker's row M-QUO in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-money · the full record, with the title as recorded, is the tracker's row M-REC in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-lib · the full record, with the title as recorded, is the tracker's row M-SAFE in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: mgmt-sched · the full record, with the title as recorded, is the tracker's row M-SCH in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: plat-host · the full record, with the title as recorded, is the tracker's row M-SIZE in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-invoice · the full record, with the title as recorded, is the tracker's row M-STA in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-10T03:45:00.000Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-time · the full record, with the title as recorded, is the tracker's row M-TIME in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: plat-web · the full record, with the title as recorded, is the tracker's row O-WEB in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-quotes · the full record, with the title as recorded, is the tracker's row GL-010 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-jha · the full record, with the title as recorded, is the tracker's row GL-011 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-contain · the full record, with the title as recorded, is the tracker's row GL-017 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: mgmt-projbook · the full record, with the title as recorded, is the tracker's row GL-018 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-inc · the full record, with the title as recorded, is the tracker's row GL-025 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-inc · the full record, with the title as recorded, is the tracker's row GL-026 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-crm · the full record, with the title as recorded, is the tracker's row GL-033 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-payroll · the full record, with the title as recorded, is the tracker's row GL-040 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: plat-launch · the full record, with the title as recorded, is the tracker's row GL-045 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row GL-046 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row GL-047 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-money · the full record, with the title as recorded, is the tracker's row GL-048 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-cost · the full record, with the title as recorded, is the tracker's row GL-049 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-lib · the full record, with the title as recorded, is the tracker's row GL-050 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-lib · the full record, with the title as recorded, is the tracker's row GL-051 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-payroll · the full record, with the title as recorded, is the tracker's row GL-052 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-lib · the full record, with the title as recorded, is the tracker's row GL-056 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-est · the full record, with the title as recorded, is the tracker's row GL-057 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row GL-058 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: plat-web · the full record, with the title as recorded, is the tracker's row GL-060 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-est · the full record, with the title as recorded, is the tracker's row GL-061 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: fin-payroll · the full record, with the title as recorded, is the tracker's row GL-062 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-lib · the full record, with the title as recorded, is the tracker's row GL-063 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row GL-064 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: mgmt-dash · the full record, with the title as recorded, is the tracker's row GL-066 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-cutover · the full record, with the title as recorded, is the tracker's row GL-068 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: safe-privacy · the full record, with the title as recorded, is the tracker's row V18 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-inc · the full record, with the title as recorded, is the tracker's row V25 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: sales-crm · the full record, with the title as recorded, is the tracker's row V27 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row V32 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row V33 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-cutover · the full record, with the title as recorded, is the tracker's row V35 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-people · the full record, with the title as recorded, is the tracker's row V40 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: safe-people · the full record, with the title as recorded, is the tracker's row V44 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: safe-people · the full record, with the title as recorded, is the tracker's row V45 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: safe-people · the full record, with the title as recorded, is the tracker's row V47 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: gear-assets · the full record, with the title as recorded, is the tracker's row V55 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: gear-qr · the full record, with the title as recorded, is the tracker's row V57 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: gear-assets · the full record, with the title as recorded, is the tracker's row V58 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: gear-assets · the full record, with the title as recorded, is the tracker's row V61 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: gear-ware · the full record, with the title as recorded, is the tracker's row V62 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: gear-ware · the full record, with the title as recorded, is the tracker's row V63 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: gear-ware · the full record, with the title as recorded, is the tracker's row V64 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row V65 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: safe-lib · the full record, with the title as recorded, is the tracker's row V67 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: sales-quotes · the full record, with the title as recorded, is the tracker's row V78 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: mgmt-docs · the full record, with the title as recorded, is the tracker's row V80 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: crew-jha · the full record, with the title as recorded, is the tracker's row V93 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: crew-jha · the full record, with the title as recorded, is the tracker's row V95 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-jha · the full record, with the title as recorded, is the tracker's row V96 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: crew-startday · the full record, with the title as recorded, is the tracker's row V100 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-contain · the full record, with the title as recorded, is the tracker's row V104 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-contain · the full record, with the title as recorded, is the tracker's row V106 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-contain · the full record, with the title as recorded, is the tracker's row V107 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-est · the full record, with the title as recorded, is the tracker's row V110 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-est · the full record, with the title as recorded, is the tracker's row V112 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: sales-est · the full record, with the title as recorded, is the tracker's row V113 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for the demo · plan card: fin-payroll · the full record, with the title as recorded, is the tracker's row V122 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row V128 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for the demo · plan card: crew-contain · the full record, with the title as recorded, is the tracker's row V131 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row P11 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: the owner · necessity: Needed for launch · plan card: fin-qbo · the full record, with the title as recorded, is the tracker's row A53 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: open · waiting on: the owner · necessity: Needed for launch · plan card: fin-cutover · the full record, with the title as recorded, is the tracker's row The owner 2 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: open · waiting on: the owner · necessity: Needed for launch · plan card: fin-cutover · the full record, with the title as recorded, is the tracker's row The owner 5 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
The 16 tracker rows waiting on both of them — a joint word closes each one. Separate from Omar's 66 and the owner's 124.
Canonical state: blocked · waiting on: Both · necessity: Needed for launch · plan card: safe-privacy · the full record, with the title as recorded, is the tracker's row GL-019 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: Both · necessity: Needed for launch · plan card: office-textline · the full record, with the title as recorded, is the tracker's row GL-020 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z
Canonical state: blocked · waiting on: Both · necessity: Needed for launch · plan card: plat-host · the full record, with the title as recorded, is the tracker's row GL-053 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: Both · necessity: Needed for launch · plan card: office-textline · the full record, with the title as recorded, is the tracker's row GL-067 in its own section
Sources and dates: materials/accounting/accounting-data.json 2026-10-11T15:54:39.756Z · outbox/homebase_makki/tracker.json 2026-10-23T22:58:49.045Z · GO_LIVE.md 2026-09-26 (written) · 2026-10-04 (State counts re-printed) · file mtime 2026-10-04T06:46:16.929Z · outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: Both · necessity: Needed for launch · plan card: office-textline · the full record, with the title as recorded, is the tracker's row V4 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: Both · necessity: Needed for launch · plan card: office-textline · the full record, with the title as recorded, is the tracker's row V7 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: Both · necessity: Needed for launch · plan card: office-msg · the full record, with the title as recorded, is the tracker's row V31 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: Both · necessity: Needed for the demo · plan card: safe-lib · the full record, with the title as recorded, is the tracker's row V88 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: Both · necessity: Needed for launch · plan card: office-textline · the full record, with the title as recorded, is the tracker's row V91 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: Both · necessity: Needed for launch · plan card: office-textline · the full record, with the title as recorded, is the tracker's row V98 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: Both · necessity: Needed for launch · plan card: office-textline · the full record, with the title as recorded, is the tracker's row V109 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: Both · necessity: Needed for launch · plan card: office-msg · the full record, with the title as recorded, is the tracker's row V114 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: partial · waiting on: Both · necessity: Needed for launch · plan card: office-msg · the full record, with the title as recorded, is the tracker's row V116 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: Both · necessity: Needed for launch · plan card: office-textline · the full record, with the title as recorded, is the tracker's row V136 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: Both · necessity: Needed for launch · plan card: office-textline · the full record, with the title as recorded, is the tracker's row V137 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
Canonical state: blocked · waiting on: Both · necessity: Needed for launch · plan card: office-textline · the full record, with the title as recorded, is the tracker's row V138 in its own section
Sources and dates: outbox/homebase_makki/tasks.json 2026-10-23T23:09:04.124Z · live snapshot of live_tasks.json (a build-box temp copy at the time) 2026-10-04T06:46:40.254Z
The same six cards as the tracker: five outcomes that add up to every live row, and the Fieldflo lens that counts no row of its own. Grouping the tasks below by project changes none of these totals.
Title as recorded on the go-live list: Emergency contact details on the man's own record — name and number of who to call; there is no edit form for a man anywhere
Wave: gl-wave1-people · status by canonical GL-003: state review, waiting on none
Title as recorded on the go-live list: Employee record depth — employee number, office / division, default cost code, union name and code, payroll group, temp-labour flag, write-ups, documents on the man, linked assets, per-employee PIN flags; the emergency contact alone is GL-003
Wave: gl-wave1-people · status by canonical GL-087: state review, waiting on none
Title as recorded on the go-live list: Cert photo on file — upload a picture of the actual ticket so the cert name on the scan opens the paper; Makki holds numbers and issuers only (the wider certificates-page depth is GL-099)
Wave: gl-wave1-people · status by canonical GL-088: state review, waiting on none
Title as recorded on the go-live list: Skills matrix and filter-by-skill dispatch — a skills list per man on top of the ticket list (Suncor orientation, a school background check) and a filter on the schedule board
Wave: gl-wave1-people · status by canonical GL-028: state review, waiting on none
Title as recorded on the go-live list: Employee safety scorecards — not present anywhere in the portal
Wave: gl-wave1-people · status by canonical GL-027: state review, waiting on none
Title as recorded on the go-live list: Disciplinary records — not present
Wave: gl-wave1-people · status by canonical GL-029: state review, waiting on none
Title as recorded on the go-live list: Export employees to CSV, and a bulk download of all QR codes; CSV export exists on Payroll only and codes come one at a time
Wave: gl-wave1-people · status by canonical GL-093: state review, waiting on none
Title as recorded on the go-live list: Editing the list of cert types — a small admin screen over the certs.js types
Wave: gl-wave1-people · status by canonical GL-004: state review, waiting on none
Title as recorded on the go-live list: Estimator and The Books on mock data — open build work, nobody blocked; the seats themselves are GL-057 and GL-058, off the board until they can work
Wave: gl-seats · status by canonical GL-059: state complete, waiting on none
Title as recorded on the go-live list: An "add" form for an asset and for an inventory line — every list in the app can be read, searched and filtered; almost none of them can be added to
Wave: gl-wave2-forms · status by canonical GL-012: state review, waiting on none
Title as recorded on the go-live list: Question templates per project: you can attach a template to a job and answer it, but nothing in the app creates or edits one — still needs a template builder
Wave: gl-wave2-forms · status by canonical GL-002: state review, waiting on none
Title as recorded on the go-live list: Building your own inspection question sets (an inspection-template builder), and an asbestos-specific inspection checklist (manometer reading, two-stage waste load-out, AHERA credential check)
Wave: gl-wave2-forms · status by canonical GL-007: state review, waiting on none
Title as recorded on the go-live list: SDS from an asset scan — link a document to an asset and put it on the scan page
Wave: gl-wave2-forms · status by canonical GL-006: state review, waiting on none
Title as recorded on the go-live list: Abatement procedure checklist on the daily — install criticals, negative pressure, construct decon, pre clean, cover fixed objects, containment, removal, bag out, final clean, clearance, tear down, demob; plus cleaning verification and cloths used. The Checker calls it the most abatement-specific thing in the whole demo; the containment log itself is GL-017
Wave: gl-wave2-forms · status by canonical GL-086: state review, waiting on none
Title as recorded on the go-live list: Meal / break attestation, and the "Were you injured?" question, on the end-of-day verify
Wave: gl-wave2-forms · status by canonical GL-036: state review, waiting on none
Title as recorded on the go-live list: Roll Call — a real-time "who has clocked in" count with a link on the dashboard, and a no-show flag; the dashboard shows "Who's on site today" from Start Day but no Roll Call link — Built 2026-09-27 (gl-wave3-board), live v30-admin 2026-10-03
Wave: gl-wave3-board · status by canonical GL-030: state review, waiting on none
Title as recorded on the go-live list: Double-booking warning in scheduling — an alert when the same employee or asset is assigned to two jobs in the same window; and the crew-projected vs crew-scheduled under-crewed warning that goes red — Built 2026-09-27 (gl-wave3-board), live v30-admin 2026-10-03
Wave: gl-wave3-board · status by canonical GL-031: state review, waiting on none
Title as recorded on the go-live list: Equipment on the schedule — assets assigned to jobs in the Gantt / week view; the scheduling board handles crews, not equipment — Built 2026-09-27 (gl-wave3-board), live v30-admin 2026-10-03
Wave: gl-wave3-board · status by canonical GL-032: state review, waiting on none
Title as recorded on the go-live list: Fieldflo dashboard rows 4–6 — the three panels after Today's projects, Nearing bid hours and Certificates expiring on their six-panel dashboard (rows 1–3 landed 09-21) — Built 2026-09-27 (gl-wave3-board), live v30-admin 2026-10-03
Wave: gl-wave3-board · status by canonical GL-016: state review, waiting on none
Title as recorded on the go-live list: Dashboard stat tiles — days without injury, client count, user count, contracts-in-progress value — Built 2026-09-27 (gl-wave3-board), live v30-admin 2026-10-03
Wave: gl-wave3-board · status by canonical GL-089: state review, waiting on none
Title as recorded on the go-live list: Equipment location map — where every vehicle, rental and piece of heavy equipment is, with rentals / heavy-equipment toggles and per-asset popups; Makki's map shows job sites, not assets — Built 2026-09-27 (gl-wave3-board), live v30-admin 2026-10-03
Wave: gl-wave3-board · status by canonical GL-085: state review, waiting on none
Title as recorded on the go-live list: Equipment maintenance and inspection engine — nearing-maintenance by trigger miles / km / hours, next inspections due, equipment corrective actions, an inspection form driven by equipment type with odometer, hours and OK / NO / N/A per line; the repair history per machine is live (GL-008) — Built 2026-09-27 (gl-wave3-board), live v30-admin 2026-10-03
Wave: gl-wave3-board · status by canonical GL-080: state review, waiting on none
Title as recorded on the go-live list: Auditors on the JHA — up to 10 extra people signing the safety meeting with their own PIN — Built 2026-09-27 (gl-wave4-jha), live v30-admin 2026-10-03
Wave: gl-wave4-jha · status by canonical GL-090: state review, waiting on none
Title as recorded on the go-live list: Evacuation plan section on the JHA, pulled from the project details — Built 2026-09-27 (gl-wave4-jha), live v30-admin 2026-10-03
Wave: gl-wave4-jha · status by canonical GL-092: state review, waiting on none
Title as recorded on the go-live list: Live weather and heat index on the JHA — current and forecast temperature, wind, humidity, a heat index, each with a "have you reviewed this with the crew" question; no earlier file records it (Part 4a) — Built 2026-09-27 (gl-wave4-jha), live v30-admin 2026-10-03
Wave: gl-wave4-jha · status by canonical GL-082: state review, waiting on none
Title as recorded on the go-live list: Voice into the daily — the crew talks into the daily report instead of typing, in any language; the foreman's voice note by text (tools/daily.cjs) is the hive's version, not the portal's — Built 2026-09-27 (gl-wave4-jha), live v30-admin 2026-10-03
Wave: gl-wave4-jha · status by canonical GL-081: state review, waiting on none
Title as recorded on the go-live list: Any language — a translate control that flips the whole portal, and a per-form globe, so a bilingual crew reads its own paperwork; nothing in the portal is translatable (the Checker's Part 4a: Fieldflo's is a Google Translate widget, not a language pack) — Built 2026-09-27 (gl-wave4-jha), live v30-admin 2026-10-03
Wave: gl-wave4-jha · status by canonical GL-079: state review, waiting on none
Title as recorded on the go-live list: Ten project-manager seats — a project-manager role between Owner and Site lead: his own jobs, his own crews, budget but not company profit; turns Team & Access from five demo logins into a roster — Built 2026-09-27 (gl-wave5-admin), live v30-admin 2026-10-03
Wave: gl-wave5-admin · status by canonical GL-013: state review, waiting on none
Title as recorded on the go-live list: Reporting Center — 18 named exportable reports (asset, job costing, expense, per diem, T&M, change order, waste, warehouse, project inventory, CRM, incident, injury, inspection, equipment log, form) — Built 2026-09-27 (gl-wave5-admin), live v30-admin 2026-10-03
Wave: gl-wave5-admin · status by canonical GL-083: state review, waiting on none
Title as recorded on the go-live list: Admin section — form sequencer, export builder, email templates and groups, email log, imports, timesheet adjuster, portal admin; the email pieces stay on the owner's rail — Built 2026-09-27 (gl-wave5-admin), live v30-admin 2026-10-03
Wave: gl-wave5-admin · status by canonical GL-084: state review, waiting on none
Title as recorded on the go-live list: Company page, Messages page, and the three-dots admin customisation on every list — Built 2026-09-27 (gl-wave5-admin), live v30-admin 2026-10-03
Wave: gl-wave5-admin · status by canonical GL-094: state review, waiting on none
Title as recorded on the go-live list: Submit a feature idea / what's new — the in-product channel Dan used to prove they listen — Built 2026-09-27 (gl-wave5-admin), live v30-admin 2026-10-03
Wave: gl-wave5-admin · status by canonical GL-091: state review, waiting on none
Title as recorded on the go-live list: A texted link that opens with no app, no account and no login — and still works when he taps it hours later: a signed, expiring web link per man per day and a page that renders with no session — Built 2026-09-27 (gl-wave5-admin), live v30-admin 2026-10-03
Wave: gl-wave5-admin · status by canonical GL-021: state review, waiting on none
Title as recorded on the go-live list: A CSV import where there is no integration — load people, customers and jobs from a spreadsheet; the backstop named on the QuickBooks screen — Built 2026-09-27 (gl-wave5-admin), live v30-admin 2026-10-03
Wave: gl-wave5-admin · status by canonical GL-015: state review, waiting on none
Title as recorded on the go-live list: "Timesheet head start + CSV import" aborted at ~46 min, no output, no reason — re-run, capture why — Built 2026-09-27 (gl-wave5-admin), live v30-admin 2026-10-03
Wave: gl-wave5-admin · status by canonical GL-077: state review, waiting on none
Title as recorded on the go-live list: HQ dashboard across branches — The owner said five companies (@2:33), Dan mentioned it at @24:23. _2026-10-04: Built on Omar's word of 04:49 UTC ("the 6 not built can you build it"), which supersedes his 09-15 close — an owner-only HQ tab rolling jobs and money up by branch with a branch switcher; branch labels are demo labels only, the real branches arrive with the owner's answers (gl-notbuilt6, PASS 96/0, v32-nb6)._
Wave: gl-037 · status by canonical GL-037: state review, waiting on none
Necessity review: 323 not-Completed rows of 566 canonical rows carry a necessity tag with a dated source — Completed 243, tagged as well (no exemption) — the not-Completed 323: Needed for the demo 223 · Needed for launch 95 · Optional 4 · Dropped 1 · Proposed 0 — the Completed 243: Needed for the demo 230 · Needed for launch 13 · Optional 0 · Dropped 0 · Proposed 0 — all 566 live rows: Needed for the demo 453 · Needed for launch 108 · Optional 4 · Dropped 1 · Proposed 0; 49 archived rows sit outside the count. On this page's 264 rows the tag is read from each row's canonical row — 93 not-Completed rows: Needed for the demo 63 · Needed for launch 27 · Optional 0 · Dropped 3 · Proposed (no source names it) 0. The owner's 19 tasks and Omar's 7 decisions are separate lists.
Superseded by the five status words on 2026-11-07; none of these is a current count. The master list's own build states — 162 built, 44 half built, 42 not built — made 74% of the build, counting 248 lines (141 walkthrough tasks, 105 pages and buttons in the app, 9 helper agents); 7 more were shown but not counted — 2 dropped on purpose, 5 not app work. 281 lines in all. The box shape on each row still shows that build state; the word beside it is the status. Since then 20 of those lines have moved under the archive on this page — merged into a surviving row, removed, or cancelled by a dated ruling — and sit in no count; the page lists 264 rows today.
History, outside every count on this page — and where an archived id is still a row above, that row names its survivor or the record it was archived via: each merged, removed or cancelled row with the row it survives as, the reason and the dated ruling — the same 49 the tracker lists under their survivors' sections.
