I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.

1

In plain terms. Should we tell the office that two renters who texted a week ago never got an answer? Clara's draft sat unapproved and expired, and staff never replied in AppFolio; telling them is one note in that customer's Slack channel.
The full question, as raised

A resident at the one customer where tenant texts are Supervised texted four times on 10-26 (conversation 408a0801-e76e-4ec4-ab3a) and has had no answer from anyone since: no staff text, no Clara send (her held reply expired unreviewed), no work order. A second (conversation 81a4696e-3d38-432f-b667, texted 10-25) got no message, though a work order of theirs completed 10-27.

Why, and what was tried
The session raising this recommends: Post one note to the office naming the two renters
Gera's 11-01 rule: an owed reply is never closed by expiry; past its bound it pages Gera. They have waited a week; a note to staff sends nothing to a resident.
Tried first, unsuccessfully: fable-decide f871dadb5 ruled: check each expired hold, raise to Gera only if a resident got no answer from anyone; the per-hold check found 1 certain, 1 possible. Posting in a customer channel is a customer-facing act, so it is Gera's.

7facb1b8 is parked on this.

2

In plain terms. Will you cancel the old Trello password in Trello's settings? It showed up in an agent's log on the mini; Trello was retired in October and nothing uses it, and after you cancel it I delete it from the mini.
The full question, as raised

A Trello API key and token were printed into a local session transcript on the mini (sent to the model provider). Fable ruled revoke (receipt f301f0125): ADR-0062 retired Trello and said the token is revoked at Trello, but the ~/.zshenv copy was missed. Revoking needs Gera's Trello login.

Why, and what was tried
The session raising this recommends: I'll cancel it in Trello; delete it from the mini
ADR-0062 already decided Trello credentials go and the token is revoked; this exposure reached the model provider's context
Tried first, unsuccessfully: fable-decide f301f0125 RESOLVED revoke; the act needs Gera's Trello login, which no agent holds

7facb1b8 is parked on this.

33 questions on this

In plain terms. Three tenant-repair changes need a founder: two fixes that each add one new alert where today nothing happens (an on-call page for an emergency on an open repair; an office email when a phone call loses a problem), and approval to mark 7,775 already-finished jobs as done.

0 of 3 answered

1PR #24442 (emergency in a two-problem tenant text lands on the right work order) was graded HIGH risk by an independent reviewer: besides aiming the emergency at the right order, it now starts the on-call alert chain when a tenant reports an emergency on an order that is already open, or on a finished repair Clara is checking in on. Before, nobody was paged in those cases. It uses the existing on-call chain (once per conversation per 24 h). Review 🟢, tests and evals green; held with hold-for-review. Grade: https://github.com/PropFlow-Technologies/propflowai/pull/24442#issuecomment-6570581532

In plain terms. Should the emergency fix go live, including the new rule that pages the on-call team when a tenant reports an emergency on a repair that is already open? Today that case pages nobody; after this, it pages the on-call chain once.
Why the raiser recommends it
The session raising this recommends: Merge the whole fix
Gera's 10-29 rule: emergencies always go out in every mode. An emergency on an open order paging nobody breaks that rule; the new page closes it through the existing chain and its 24 h limit.

2PR #24458 (a problem a tenant raises on a phone call is never silently dropped) was graded HIGH risk by an independent reviewer because it adds a NEW email to the building's office: when a finished call leaves a problem undecided, the office gets one note per call naming the problem(s) with a link to the call. It goes through the standard staff-note door: Off sends nothing, Supervised and Preview hold it for approval, Live sends it. Expected rare (0 such calls in 32 days). Review 🟢, tests green; held with hold-for-review. Grade: https://github.com/PropFlow-Technologies/propflowai/pull/24458#issuecomment-6571400107

In plain terms. Should a caller's lost repair problem now email the building's office, once per call with a link? Today it just disappears; this note is held for approval wherever approval mode is on.
Why the raiser recommends it
The session raising this recommends: Merge it
Gera's 11-01 rule: an owed reply is never silently dropped. It reaches only the building's own office, through the mode-gated door, and is expected to be rare.

3Approve running the merged cleanup script on prod, exactly: from a fresh origin/main worktree at or after 14cc986a8f0, after a fresh plain dry run taken just before still reads 7,775: `DATA_BACKEND=dynamodb DYNAMODB_TABLE_NAME=propflow-prod AWS_REGION=us-east-1 npx tsx scripts/remap-wo-status-from-appfolio.ts --apply --confirm-table=propflow-prod --approved-by="<founder name>: <their words>" --expect=7775`. Dry run 2026-11-02T09:17Z on main: 7,775 work orders AppFolio already reports finished move from open to completed: org_a3376147 6,898 (Work Done 6,897, Completed 1), org_c42d9150 868 (Completed No Need To Bill), org_jpco 9 (Completed). Checked at 09:19Z for all 7,775: every one created over 90 days ago (youngest 94.1 days), none has a completion date, none was ever sent a rating request or a repair check-in, none has a rating. Status only: no completion date, no signal, no AppFolio write, so no texts can fire; each row gets an undo record; --undo's archived-row fix is PR #24468 (graded low, armed). Excluded: 3 orders with a pending AppFolio update, every 'would reopen' bucket (225), unknown statuses (48). Effect people see: residents' 'my work orders' list, Clara's open-order context and staff dashboard counts drop these 7,775 old jobs. If the count moves before the run (the nightly refresh keeps storing statuses), the script refuses and this needs re-approval. PR: https://github.com/PropFlow-Technologies/propflowai/pull/24451

In plain terms. Should this session mark 7,775 repair jobs done that AppFolio already shows as finished? It texts no one, can be undone, and only removes old jobs from open lists; it runs only on Gera's or Fede's go for this exact command.
Why the raiser recommends it
The session raising this recommends: Approve the exact command
The jobs are finished in AppFolio and all over 90 days old; the change is status-only, reversible and sends nothing; it removes stale orders Clara, residents and staff see as open.
Why, and what was tried
Tried first, unsuccessfully: Not asked: the 10-31 risk rule routes a HIGH grade to both founders, and a large prod-data change needs a founder's direct approval of the exact step (CLAUDE.md hard floor). Re-raised because block b93603974 was withdrawn by mistake while replacing its stale 4,629 count.

7facb1b8 is parked on this.

Answered and withdrawn (2)
Pick an option above, then press Done.
PropFlow Docs