Read status
liveLoading the current intake packet.
PM Review Promotion
Loading PM drivers route.
Preparing the promoted PM drivers review slice inside the governed shell.
PM Review Promotion
Preparing the promoted PM drivers review slice inside the governed shell.
Project Miner Intake Workbench
One read-only PM starting point for the current candidate, import gate, approval contract, and storage plan. It consolidates review context without approving, persisting, importing, assigning, scheduling, changing status, or mutating production state.
Loading the current intake packet.
Unknown project - unknown location
No approval storage table is admitted.
Hosted PM intake reads, approval status readback, approval route registration, and bounded MCP read proof are green.
Review the source-derived project shape, current gates, and guardrails before moving to any dedicated detail route.
0 proposed groups.
0 proposed task rows.
0 candidate apparatus rows.
0 warnings, 0 blockers, 0 human decisions.
Fast local navigation for the current intake workbench. These links do not approve, persist, import, assign, schedule, change status, create tasks, create issues, call live services, or mutate production state.
Compact top-of-page scan for the current local PM move, next field question posture, handoff context, and blocked future authority. It does not approve, persist, import, assign, schedule, change status, create tasks, create issues, call live services, perform hosted writes, or mutate production state; it creates no localStorage key, export artifact, backend route, schema, approval record, durable field record, production tracking row, or production write.
Do now
current import-intake candidate: start with source and exception review. Source fingerprint source fingerprint pending; review checklist has 0 of 7 local checks marked and exceptions are 2 covered, 3 open, 1 blocked.
Ask next
Field prep queue is 0 complete / 1 next / 4 blocked. Capture field questions draft: Capture drawing/source, access/safety, material, customer, or PM follow-up questions before the kickoff brief is used.
Prepare handoff context
Use the output selector after local decision notes, field questions, observation notes, or executor closeout evidence exist.
Still blocked
4 of 6 approval-persistence gates remain blocked and project import remains not admitted.
Conversation-ready local summary for PM, lead, customer, or field review. It does not approve, persist, import, assign, schedule, change status, create tasks, create issues, call live services, perform hosted writes, or mutate production state; it creates no localStorage key, export artifact, backend route, schema, approval record, durable field record, production tracking row, or production write.
Project readout
current import-intake candidate in unknown location: 0 workpackages, 0 tasks, and 0 apparatus candidates are loaded from source fingerprint source fingerprint pending.
Review posture
Exceptions are 2 covered, 3 open, 1 blocked and local review notes have not started.
Field ask
Field prep is 0 complete / 1 next / 4 blocked. Capture field questions draft: Capture drawing/source, access/safety, material, customer, or PM follow-up questions before the kickoff brief is used.
Boundary statement
4 of 6 approval-persistence gates remain blocked; project import remains not admitted; executor closeout evidence is 0 of 8.
Constraint scan for source/review, field-prep, executor/hosted, and future write-authority boundaries. It does not approve, persist, import, assign, schedule, change status, create tasks, create issues, call live services, perform hosted writes, or mutate production state; it creates no localStorage key, export artifact, backend route, schema, approval record, durable field record, production tracking row, workbook macro path, workbook writeback, or production write.
Source and review constraints
Source fingerprint source fingerprint pending; review checklist has 0 of 7 local checks marked; exceptions are 2 covered, 3 open, 1 blocked; local review notes have not started.
Field-prep constraints
Field prep is 0 complete / 1 next / 4 blocked. Field questions present: no; field observations present: no.
Executor and hosted constraints
Executor closeout intake is 0 of 8; hosted read, schema, approval status, and bounded MCP proof are green while closeout checks remain audit-prep context only.
Future write authority constraints
4 of 6 approval-persistence gates remain blocked; project import remains not admitted; future write authority remains outside this browser-local workbench.
First 5 minutes of browser-local review, derived from the existing workbench state. It creates no localStorage key, export artifact, backend route, schema, approval record, task, issue, schedule, status, durable field record, production tracking row, hosted write claim, or production write.
Minute 0: Confirm source context
current import-intake candidate: source fingerprint source fingerprint pending; candidate authority remains not admitted.
Minute 1: Scan exceptions
Import exception register: 2 covered, 3 open, 1 blocked.
Minute 2: Capture local draft notes
Local decision draft has not started; capture decision value, review notes, and local-only attestation before any future persistence packet.
Minute 3: Check field-prep questions
Field prep queue: 0 complete / 1 next / 4 blocked. Capture field questions draft: Capture drawing/source, access/safety, material, customer, or PM follow-up questions before the kickoff brief is used.
Minute 4: Name blocked future authority
0 of 8 local closeout evidence checks are marked; 4 of 6 approval-persistence gates remain blocked and project import remains not admitted.
Morning-of field-start conversation script derived from existing local prep state. It creates no localStorage key, export artifact, backend route, task, issue, field authorization, assignment, schedule/status change, durable field record, production tracking row, hosted write claim, or production write.
Say field-start posture
current import-intake candidate: field-start preflight is field-start preflight pending; field start authority remains not admitted.
Check source and access questions
Capture drawing/source and access/safety questions before field reliance.
Walk queue, coverage, and agenda
Field prep queue: 0 complete / 1 next / 4 blocked. Coverage: 0 covered, 0 partial, 5 open, 2 blocked. Agenda: 0 context, 5 ask, 0 confirm, 2 blocked.
Export context only
Use import-intake-field-start-preflight.json or import-intake-field-prep-packet.md as local conversation context; do not treat exports as authorization.
Stop line before field authority
Do not approve, import, authorize field work, assign crews, schedule/status work, create durable field records, or start production tracking from this workbench. Field observations present: no.
Morning-of Temp Power stop-line check for the field-start conversation. It creates no approval, import, field, production, customer, or finance write; no localStorage key, export artifact, backend route, approval row, field authorization, assignment, schedule/status change, durable field record, production tracking row, customer report, finance output, hosted write claim, or production write.
Field authority stop line
current import-intake candidate: field start authority remains blocked until field authority and tracking packet; preflight is field-start preflight pending.
Assignment, schedule, and status stop line
Do not assign leads or crews, schedule work, alter status, or direct field execution from this workbench.
Durable record and production stop line
Do not create durable field records, production quantities, progress rows, completion evidence, or customer-facing production truth.
Customer and finance stop line
Do not create customer reports, billing exports, payroll exports, invoices, accounting postings, or external finance-system syncs.
Context-only use
Use the operator script and local exports only as conversation context; 0 blocked boundaries remain outside this browser-local review.
Morning-of Temp Power customer/site question review derived from existing field questions and observations. It creates no localStorage key, export artifact, backend route, task, issue, assignment, schedule/status change, customer commitment, customer report, field instruction, hosted write claim, or production write.
Site access and safety questions
current import-intake candidate: capture site access, escort, safety, or LOTO questions before the field-start conversation; do not turn them into instructions or commitments here.
Customer constraint questions
Customer/site constraint questions are still open; ask about access windows, shutdown constraints, escort requirements, and site contact questions as conversation context only.
Material and staging questions
Material, equipment, and staging questions are still open; keep them as local prep questions until a later approved field packet exists.
Drawing and source questions
Drawing/source questions are still open; review source truth before any future field-authority packet.
PM follow-up and customer commitment boundary
No PM follow-up/customer-site context is captured yet; do not turn questions into owner lists, assignments, customer commitments, customer reports, schedule/status changes, or field direction from this workbench.
Copy/paste prompt review for the next PM, lead, or customer question after the customer/site check. It creates no localStorage key, export artifact, backend route, task, action item, owner, due date, customer commitment, hosted write claim, or production write.
PM follow-up question prompt
current import-intake candidate: PM follow-up prompt is open; decide the next PM question before accountability, timing, field instruction, customer commitment, or status language is discussed.
Customer/site return prompt
Return to site access, escort, shutdown-window, and contact-path questions before relying on field assumptions.
Lead conversation prompt
Lead prompt is open; start with source, access, material, equipment, and staging unknowns before field reliance.
Evidence/source prompt
Evidence/source prompt is open; identify what source record or site note should be checked before a later bounded packet.
Next packet boundary prompt
If the follow-up needs accountability, timing, customer-facing language, field direction, report, schedule/status update, or durable record, stop here and author a later bounded packet; this section records none.
Copy/paste review context for what to bring back after the field-start conversation. It creates no meeting note, localStorage key, export artifact, backend route, task, action item, owner, due date, customer commitment, customer report, field instruction, hosted write claim, or production write.
Conversation summary return prompt
current import-intake candidate: after the field-start conversation, bring back a short summary of what changed and what stayed open; do not store the summary in this panel.
Customer/site return closeout prompt
Customer/site return remains open; ask what access, shutdown, escort, or contact answer still needs local review before any later bounded packet.
Lead/resource return closeout prompt
Lead/resource return remains open; ask what material, equipment, staging, or lead clarification should be reviewed locally before field reliance.
Evidence/source return prompt
Evidence/source return remains open; identify the source record, drawing, workbook row, or site note to inspect before any later authority packet.
Next packet closeout boundary
If the conversation reveals a needed next move, bring back only the packet question; do not turn it into work lists, accountability fields, timing fields, commitments, reports, or writes here.
Compact read-only triage strip for returned field-start conversation context. It summarizes which bring-back areas currently have local context only before the detailed queue and lenses; it creates no meeting note, localStorage key, export artifact, backend route, task, action item, owner, due date, assignment, schedule/status write, customer commitment, customer report, field instruction, durable record, production tracking row, hosted write claim, or production write, and exposes no buttons.
Source review context
current import-intake candidate: no returned source-review context is captured yet; if one returns, use the source lens before any later packet.
Customer/site clarification context
No returned customer/site clarification context is captured yet; if one returns, keep it local until a later bounded packet admits more.
Lead/resource clarification context
No returned lead/resource clarification context is captured yet; if one returns, keep it as browser-local review context only.
Later bounded packet candidate context
No later bounded packet candidate context is captured yet; if one returns, classify the packet question without creating work here.
Compact read-only jump rail from the summary triage strip to the exact bring-back detail lens. It only navigates within this browser-local review panel; it creates no meeting note, localStorage key, export artifact, backend route, task, action item, owner, due date, assignment, schedule/status write, customer commitment, customer report, field instruction, durable record, production tracking row, hosted write claim, or production write, and exposes no buttons.
Open-context cue
Populated detail lens context: none yet. Keep returned field-start details local until a later bounded packet admits more. This is a browser-local open-context cue only. It shows which existing bring-back detail lens currently has local context; it creates no meeting note, localStorage key, task, action item, owner, due date, assignment, customer commitment, customer report, field instruction, durable field record, production tracking row, report, export artifact, storage key, backend route, button, hosted write claim, or write path.
Review order hint
Review first: Source review lens when returned context names a drawing, workbook row, site note, observer/source, or work-area reference; then customer/site clarification; then lead/resource clarification; use the later bounded packet candidate lens only to classify a future packet question. Browser-local display hint only; creates no link, button, localStorage key, sessionStorage key, task, action item, owner, due date, assignment, schedule/status write, customer report, field instruction, export artifact, backend route, hosted write claim, or write path.
Cue status legend
Display-only legend for the bring-back cue and detail jump statuses. It explains existing status words only; it creates no meeting note, link, button, localStorage key, sessionStorage key, task, action item, owner, due date, assignment, schedule/status write, customer commitment, customer report, field instruction, durable record, production tracking row, report, export artifact, backend route, hosted write claim, or write path.
Context means populated source-review local context exists; review the matching lens before any later bounded packet.
Review means populated clarification context exists; inspect the matching lens locally before field reliance.
Open means no returned context is captured yet; keep any future return browser-local until admitted.
Blocked means a later bounded packet may be needed; classify only the packet question here.
Read-only bring-back queue for returned field-start conversation items. It classifies local review context only and creates no meeting note, localStorage key, export artifact, backend route, task, action item, owner, due date, customer commitment, customer report, field instruction, hosted write claim, or production write.
Source review
current import-intake candidate: if the conversation returns a drawing, workbook row, site note, observer/source, or work-area question, classify it as local source review only.
Customer/site clarification
If the conversation returns access, shutdown, escort, contact, safety, or constraint answers, classify them as customer/site clarification only.
Lead/resource clarification
If the conversation returns lead, material, equipment, staging, or crew-readiness context, classify it as lead/resource clarification only.
Later bounded packet candidate
If a returned item needs a move beyond local review, classify only the packet question; do not create work lists, timing fields, commitments, reports, records, or writes here.
Read-only source review lens for returned field-start conversation items. It helps classify drawings, workbook rows, site notes, observer/source context, and work-area references before any later bounded packet; it creates no meeting note, localStorage key, export artifact, backend route, task, action item, owner, due date, customer commitment, customer report, field instruction, durable record, hosted write claim, or production write.
Drawing/workbook source check
current import-intake candidate: if the return names a drawing, workbook row, or estimator source, check source lineage before any later bounded packet.
Site note source check
If the return is a site note, access observation, safety observation, or material/equipment note, classify it for local source review before field reliance.
Observer/source context check
If the return depends on who said it or when it was discussed, keep that question outside this lens and classify it for source review only.
Work-area reference check
If the return names an area, workpackage, apparatus, or location reference, check it against source context before any later packet.
Source review packet boundary
If a returned source item needs more than local review, classify only the packet question; do not create records, tasks, timing fields, commitments, reports, or writes here.
Read-only customer/site clarification lens for returned field-start conversation items. It helps classify access, shutdown, escort, contact, safety, and constraint answers as browser-local review context only; it creates no meeting note, localStorage key, export artifact, backend route, task, action item, owner, due date, customer commitment, customer report, field instruction, durable record, hosted write claim, or production write.
Access/shutdown answer check
current import-intake candidate: if the return names access, shutdown, escort, gate, badge, or site-entry details, keep it as customer/site clarification only.
Escort/contact path check
If the return depends on a customer contact, site escort, observer, or conversation timing, keep that context local and do not assign ownership here.
Safety/LOTO clarification check
If the return names safety, LOTO, PPE, escort, or access restrictions, classify it for local customer/site clarification before field reliance.
Constraint answer boundary
If the return names shutdown windows, outage constraints, access hours, timing assumptions, or customer-facing language, classify only the packet question.
Customer/site promise stop line
current import-intake candidate: if a returned customer/site answer needs accountability, timing, customer-facing language, field direction, report, schedule/status update, durable record, or write authority, stop and author a later bounded packet; do not create promises here.
Read-only lead/resource clarification lens for returned field-start conversation items. It helps classify lead, crew-readiness, material, equipment, staging, and resource-limit details as browser-local review context only; it creates no meeting note, localStorage key, export artifact, backend route, task, action item, owner, due date, assignment, schedule/status write, customer commitment, customer report, field instruction, durable record, production tracking row, hosted write claim, or production write, and exposes no buttons.
Lead conversation source check
If the return depends on who said it or when it was discussed, classify it as lead/resource clarification only and do not assign ownership here.
Crew readiness clarification check
If the return names crew count, role mix, readiness, tooling, or lead availability, classify it as lead/resource clarification only before field reliance.
Material/equipment clarification check
If the return names material, rental, equipment, tooling, delivery, or receiving details, classify it as lead/resource clarification only before any later packet.
Staging/resource limit check
If the return names laydown, staging, access-for-equipment, work area, or resource limits, keep it as browser-local review context only.
Lead/resource authority stop line
current import-intake candidate: if a returned lead/resource answer needs a task, action item, owner, due date, assignment, timing field, schedule/status write, durable record, production tracking, report, export, backend route, storage key, button, or write authority, stop and author a later bounded packet; do not create it here.
Read-only later bounded packet candidate lens for returned field-start conversation items. It helps classify whether a returned item needs a future packet for authority, evidence, owner/timing, customer-facing language, or write-path admission; it creates no meeting note, localStorage key, export artifact, backend route, task, action item, owner, due date, assignment, schedule/status write, customer commitment, customer report, field instruction, durable record, production tracking row, hosted write claim, or production write, and exposes no buttons.
Future packet boundary reminder
PM Lane 203 reminder: this lane classifies a future bounded packet question only. It does not create the packet, assign accountability, set timing, write status, direct field work, create customer-facing language, publish reports, create storage, call a backend route, expose controls, or admit any write path.
Future packet trigger check
If the return needs a move beyond local review, classify only the future packet question; do not create work lists, timing fields, commitments, reports, records, or writes here.
Authority admission check
If the return needs approval submission, import, field authorization, assignment, schedule/status, durable record, production tracking, report, or billing authority, stop and author a later bounded packet.
Evidence/context check
If the return depends on a drawing, workbook, site note, observer, work area, or source record, classify the evidence needed for the future packet without storing it here.
Owner/timing language check
If the return needs owner, due date, timing, customer-facing language, field direction, or accountability, classify only that future-packet need and keep this section read-only.
Bounded packet stop line
current import-intake candidate: if a returned item needs a task, action item, owner, due date, assignment, timing field, schedule/status write, customer commitment, customer report, field instruction, durable record, production tracking, export, backend route, storage key, button, or write authority, stop and author a later bounded packet; do not create it here.
PM Lane 204 cue: before leaving this bring-back panel, keep the return as browser-local review only. Classify what still belongs in source review, customer/site clarification, lead/resource clarification, or future packet classification; do not record meeting notes, create tasks, assign owners, set dates, direct field work, publish reports, call routes, create storage, export artifacts, expose controls, or admit write paths.
PM Lane 205 summary: leave this panel with four browser-local classifications only: source review, customer/site clarification, lead/resource clarification, and future packet question. Anything needing approval submission, import, assignment, schedule/status, field direction, customer report, storage, export, route, control, or write authority needs a later bounded packet.
Top-level focus for this intake session, derived from the existing workbench state. It does not approve, persist, import, assign, schedule, change status, create tasks, create issues, call live services, or mutate production state. It links to existing local sections and exports only; it creates no localStorage key, export artifact, backend route, schema, approval record, task, issue, or production write.
First local move
Review source and exceptions: Start with source freshness and warning review before relying on the candidate shape.
Exception attention
Import exception register: 2 covered, 3 open, 1 blocked.
Field-prep focus
Capture field questions draft: Capture drawing/source, access/safety, material, customer, or PM follow-up questions before the kickoff brief is used.
Useful local export
Use Export PM Brief first when the next review needs compact candidate, gate, and guardrail context.
Blocked future authority
4 of 6 approval-persistence gates remain blocked. Snapshot posture: 1 covered, 4 open, 1 blocked.
Browser-local chooser for existing outputs already on this workbench. It creates no localStorage key, export artifact, backend route, schema, approval record, task, issue, schedule, status, durable field record, production tracking row, hosted write claim, or production write.
PM Brief
Use PM Brief when the next review needs compact candidate, gate, and guardrail context.
Approval Preview JSON
Approval Preview JSON should wait on local decision value, review notes, local-only attestation, and checklist evidence for useful later-packet context.
PM Intake Snapshot
Use PM Intake Snapshot when the next review needs a compact local scan of exception posture, field prep, hosted parity, and blocked write boundaries.
Import Exception Register
Use Import Exception Register when the next review needs source freshness, warning signals, human decisions, and no-go checks in one local view.
Field Kickoff Brief
Field Kickoff Brief is most useful after field questions or readiness evidence are captured; current field prep queue is 0 complete / 1 next / 4 blocked.
Field Observation Notes
Use Field Observation Notes when local day-one observation context has been captured for PM and lead conversation prep.
Field Prep Coverage Snapshot
Use Field Prep Coverage Snapshot when the next conversation needs source, access, material, crew, authority, and production-boundary coverage context; field prep queue is 0 complete / 1 next / 4 blocked.
Field Prep Conversation Agenda
Use Field Prep Conversation Agenda when the next conversation needs context, asks, confirmations, and blocked boundary prompts grouped for review.
Field Prep Packet
Field Prep Packet is the bundled field-prep artifact when the next conversation needs questions, coverage, agenda, readiness evidence, and observation context; current field prep queue is 0 complete / 1 next / 4 blocked.
Field Start Preflight
Use Field Start Preflight as browser-local readiness context before any later packet admits field authority or production tracking.
Field Execution Gate Design
Use Field Execution Gate Design when the next packet needs the no-write bridge toward later approval, import, field, and production admission.
Lead Field Assignment Draft
Use Lead Field Assignment Draft for PM and lead review before any assignment, authorization, schedule, status, or durable record write is admitted.
Field Authorization Assignment Draft
Use Field Authorization Assignment Draft as packet-design context only; it does not authorize work or assign people.
Schedule Status Controls Draft
Use Schedule Status Controls Draft to review later schedule/status proof needs while schedule and status mutations stay blocked.
Durable Field Record Draft
Use Durable Field Record Draft to review later daily record proof while durable record, evidence, production, customer, and finance writes stay blocked.
Production Tracking Draft
Use Production Tracking Draft to review later quantity, labor, apparatus, progress, audit, and readback proof while production tracking stays blocked.
Customer Reporting Draft
Use Customer Reporting Draft to review later report and completion evidence proof while customer-facing outputs stay blocked.
Financial Handoff Draft
Use Financial Handoff Draft to review later billing, payroll, invoice/accounting, labor reconciliation, audit, and readback proof while finance writes stay blocked.
Pilot Launch Binder
Use Pilot Launch Binder when the next review needs one bundled local context across approval preflight, field start, admission drafts, and blocked boundaries.
Pilot Launch Daily Brief
Use Pilot Launch Daily Brief when the next PM, lead, or customer conversation needs a compact today-focused review sequence.
Pilot Launch Standup Card
Use Pilot Launch Standup Card when the next conversation needs role-based talk tracks, no-go checks, and local capture prompts.
Pilot Launch Capture Sheet
Use Pilot Launch Capture Sheet when the next meeting needs blank local prompts for PM decisions, blockers, customer/site questions, and executor follow-up.
Pilot Launch Follow-Up Packet
Use Pilot Launch Follow-Up Packet when the next review needs copy/paste return sections for VS Code Codex, Desktop Codex, or sidecar scout closeout.
Browser-local guide for the next context lane. It creates no localStorage key, export artifact, backend route, schema, approval record, task, issue, schedule, status, durable field record, production tracking row, hosted write claim, or production write.
Field conversation prep
Field prep queue is 0 complete / 1 next / 4 blocked. Capture field questions draft: Capture drawing/source, access/safety, material, customer, or PM follow-up questions before the kickoff brief is used.
Bounded executor context
Keep executor context local until review notes, local decision context, or closeout evidence are present.
Hosted readiness context
Hosted Vercel, Render, approval status readback, and bounded MCP proof are green; this local workbench still grants no browser write authority.
Future approval-persistence packet boundary
4 of 6 approval-persistence gates remain blocked and project import remains not admitted.
Visual map of the current intake path from source review through field-prep context, executor closeout, and still-blocked future write authority. It creates no localStorage key, export artifact, backend route, schema, approval record, task, issue, or production write.
Exception-first lens for local attention items and future authority blockers. It creates no localStorage key, export artifact, backend route, schema, approval record, task, issue, work authorization, or production write.
Compact scan view for exception posture, decision draft, field-prep context, next local action, hosted parity, and future write boundaries. It does not approve, persist, import, assign, schedule, change status, create tasks, create issues, or mutate production state.
1 covered, 4 open, 1 blocked
Exception review snapshot
Import exception register: 2 covered, 3 open, 1 blocked.
Open local exception evidence remains in the register.
Decision draft snapshot
Decision value, review notes, and local-only attestation still need local draft context.
Decision draft: none selected
Field prep snapshot
Coverage snapshot: 0 covered, 0 partial, 5 open, 2 blocked. Conversation agenda: 0 context, 5 ask, 0 confirm, 2 blocked.
Field readiness checks: 0 of 8; field questions draft: no; observation scratchpad: no.
Next local action snapshot
Review source and exceptions: Start with source freshness and warning review before relying on the candidate shape.
Executor closeout intake: 0 of 8 checked.
Approval persistence boundary
Approval persistence readiness gates: 2 of 6 ready.
Hosted schema and approval route gates are ready; browser approval submission, first approval row creation, and import mutation remain blocked.
Hosted parity boundary
Hosted PM intake, mutation-seam reads, approval status readback, and bounded Supabase MCP read proof are green.
PM Lane 041A/041B/041C/138 plus control-plane pooler maintenance closed the hosted read and schema gates.
Local queue for today's intake work. It translates the checklist, local decision draft, and readiness gates into practical next moves without approving, persisting, importing, assigning, scheduling, changing status, or mutating production state.
1 complete / 1 next / 5 blocked
Review source and exceptions
Start with source freshness and warning review before relying on the candidate shape.
Prepare local decision draft
Capture at least one local checklist item before preparing the decision draft.
Export review artifacts
Complete local checklist evidence and the decision draft before treating exports as packet context.
Hosted approval gate complete
Hosted schema, approval status readback, approval POST route registration, and bounded MCP read proof are green with zero approval records for this candidate.
Browser approval submission packet
A later packet must admit the browser approval control, live POST evidence, idempotent row creation, and rollback/return handling.
Approval row creation
The approval table is empty by proof; this workbench must not create the first hosted approval row.
Project import packet
Project, workpackage, task, and apparatus rows remain blocked until approval submission has been admitted and audited in a separate packet.
Derived exception register for candidate warnings, human decision prompts, admission no-go checks, local review evidence, and local decision draft context. It does not approve, persist, import, assign, schedule, change status, create tasks, create issues, or mutate production state.
2 covered, 3 open, 1 blocked
Source freshness evidence
Mark source freshness review before relying on the candidate shape for later packet context.
unknown fingerprint
Candidate warning signals
No candidate warnings are currently reported.
none reported
Human decision prompts
No human decision prompts are currently reported.
none reported
Local decision draft evidence
Prepare a local decision value, review notes, and local-only attestation for future packet context.
Decision draft: none selected; Project Data Entry exact label: not required for current candidate; notes: none entered; attestation: no
Admission no-go checks
Admission no-go checks need local PM review before any later import packet.
none reported
Future write boundary
Approval persistence, import rows, assignment, schedule, status, issue, task, durable field record, and production tracking writes remain blocked.
A later packet must explicitly admit any write path before implementation.
Source intake
Read-only source freshness is waiting for the candidate read.
Candidate review
Exception review stays at /pm-review/import-candidate before any import approval is admitted.
Admission gate
The admission plan defines idempotency, diff checks, target rows, and no-go checks before write authority exists.
Approval readiness
Approval readback is waiting for approval status read; browser approval submission and future import remain blocked at not admitted.
Hosted parity
PM Lane 041A/041B/041C/138 plus control-plane pooler maintenance proved hosted reads, schema, approval status readback, approval POST registration, and bounded MCP read proof; browser approval submission remains blocked.
Future import
Project, workpackage, task, apparatus, assignment, schedule, and status writes remain blocked.
No candidate warnings are currently reported.
No PM decisions are currently reported.
Status readback only. This panel does not approve, persist, import, assign, schedule, change status, or mutate production state.
waiting for task-plan status read. Durable task-plan rows preserve PM grouping context only; they do not approve, import, assign, schedule, change status, or mutate production state.
Browser-local review prep only. Checking these items does not approve, persist, import, assign, schedule, change status, or mutate production state.
Draft the future approval decision and notes for the PM brief only. This does not approve, persist, import, assign, schedule, change status, or mutate production state.
Builds the future approval POST envelope in this browser for review only. It does not call live services, perform hosted writes, create an approval record, import project rows, assign work, schedule work, change status, or mutate production state.
Candidate identity or source fingerprint is missing; the dry-run envelope should not be used as packet context yet.
Mark source freshness and warning review before treating the envelope as review-ready.
Decision value, review notes, and local-only attestation are needed before this dry run is useful packet context.
No admission no-go checks are reported for the current candidate.
Approval status readback has not loaded yet.
The exact PM Lane 142 live-write admission phrase is still required before any browser approval POST, approval-row creation, or project import.
not admitted
Decision value, review notes, and local-only attestation are needed before this dry run is useful packet context.
Browser approval submission, first approval-row creation, and project import remain blocked until a separate explicit admission.
No local dry run has been built for this browser session.
Browser-local audit prep for external executor returns. Checking these items does not accept, approve, persist, deploy, import, assign, schedule, change status, or mutate production state.
Browser-local prep evidence for PM, lead, and field review conversations. Checking these items does not authorize work, approve, persist, import, assign, schedule, change status, or mutate production state.
Browser-local question notes for PM, lead, and field prep conversations. These notes do not create tasks, issues, work authorization, assignments, schedules, status updates, approval records, imports, or production writes.
Derived queue for field-prep conversations. It translates local field questions and readiness evidence into practical next moves without creating tasks, issues, assignments, schedules, status updates, approval records, import rows, or production writes.
0 complete / 1 next / 4 blocked
Capture field questions draft
Capture drawing/source, access/safety, material, customer, or PM follow-up questions before the kickoff brief is used.
Mark field readiness prep evidence
Capture field questions before marking readiness evidence as useful prep context.
Export field kickoff prep brief
Field questions and readiness evidence are needed before the kickoff brief has useful prep context.
Confirm field authority boundary
Field authority boundary review waits for field questions and readiness evidence.
Production execution tracking
No issue, task, assignment, schedule, status, import, approval, or production tracking write is admitted by this local workbench.
Browser-local coverage snapshot derived from existing local prep state. It shows what field-prep context is covered, partial, open, or blocked without creating tasks, issues, work authorization, assignments, schedules, status updates, approval records, import rows, durable field records, production tracking rows, or production writes.
0 covered, 0 partial, 5 open, 2 blocked
Source and drawing coverage
Uses the drawing/source readiness check and drawing/source question text as browser-local conversation coverage.
Access and safety coverage
Uses the safety planning readiness check plus site/access/safety questions or access/safety observation notes.
Crew and equipment coverage
Uses the crew/equipment readiness check and crew/equipment question text as local prep coverage.
Material and staging coverage
Uses the material/staging readiness check plus material/staging questions or material/equipment observation notes.
Customer constraint coverage
Uses the customer constraint readiness check and customer constraint question text as local prep coverage.
Field authority boundary
Boundary acknowledgement remains blocked until explicitly checked; local prep does not authorize work.
Production tracking boundary
Production tracking remains blocked until a later packet explicitly admits the required write path.
Browser-local agenda derived from the coverage snapshot. It turns covered, partial, open, and blocked prep areas into conversation context, ask, confirm, and blocked agenda items without creating tasks, issues, work authorization, assignments, schedules, status updates, approval records, import rows, durable field records, production tracking rows, or production writes.
0 context, 5 ask, 0 confirm, 2 blocked
Source and drawing coverage
Ask PM, lead, customer, or field contact for source and drawing coverage context before the next field-prep conversation.
Access and safety coverage
Ask PM, lead, customer, or field contact for access and safety coverage context before the next field-prep conversation.
Crew and equipment coverage
Ask PM, lead, customer, or field contact for crew and equipment coverage context before the next field-prep conversation.
Material and staging coverage
Ask PM, lead, customer, or field contact for material and staging coverage context before the next field-prep conversation.
Customer constraint coverage
Ask PM, lead, customer, or field contact for customer constraint coverage context before the next field-prep conversation.
Field authority boundary conversation
Boundary conversation waits for at least one local field-prep coverage area.
Production tracking boundary
Keep production execution tracking blocked until a later packet explicitly admits the required write path.
Browser-local observation notes for PM, lead, and field conversations. These notes do not create tasks, issues, work authorization, assignments, schedules, status updates, approval records, imports, or production writes.
Local readiness map for the future approval-persistence packet. It reflects review context and blockers only; it does not approve, persist, import, assign, schedule, change status, or mutate production state.
PM Lane 138 closed the hosted schema gate with zero approval rows, and the bounded Supabase MCP read path is restored. Browser approval submission and import mutation remain blocked until later packets explicitly admit them.
Readback is informational only; project import remains blocked until a later packet explicitly admits that write path.
Approval preview context
Prepare a complete local decision draft before treating the preview as later packet context.
Review checklist evidence
Use the local checklist before relying on the preview as review context.
Hosted schema gate
PM Lane 138 applied migration 003 on hosted Supabase and proved the approval table plus insert-only triggers; current readback shows 0 approval records for this candidate.
Hosted approval route gate
Hosted mutation-seam exposes approval status readback and the PM-only approval POST route, but this workbench does not call that POST.
Browser approval submit authority
No browser approval button, approval POST wiring, or live approval-row creation is admitted until a later packet owns that UI submission path.
Import mutation authority
Project, workpackage, task, and apparatus import remain blocked until a later packet admits import after an approved approval record exists.