Prompts library

This is a first draft for 14–20 September 2026, pending your answers below.

Every day: sleep 23:00–07:00, lunch 12:00–13:00, and dinner 18:00–19:00 are protected. Flexible work stays within 09:00–17:00.

Assumptions

• “Work tasks only 09:00–17:00” applies to active tasks; Monday’s 08:45 transition is protected preparation-free time, not extra work.
• Setup, workshop, and cleanup form one continuous fixed event; the Wednesday travel and visit similarly form one continuous block. Buffers sit outside these blocks.
• Each flexible task occurs once. The handout finishes Tuesday, ahead of Friday 17:00. Supply collection’s 60 minutes is provisionally treated as the full task, including any travel; extra travel has not been invented.
• Unassigned time stays unassigned; Sunday afternoon is not assumed available.

The two tradeoffs that matter most

1. Using Tuesday and Thursday mornings for the handout and budget protects your strongest focus time, but leaves less of that time for anything unexpected.
2. Friday supply collection keeps the earlier week light, but leaves little recovery time if supplies are unavailable before Saturday.

Two questions before finalizing

1. Does the 60-minute supply collection estimate include travel, and would you prefer it earlier in the week to allow time for shortages?
2. Is a protected 08:45–09:00 transition acceptable on Monday, or does the 09:00 boundary also prohibit reserving transition time before work?

Hall A is the provisional choice; Hall B could rank higher if its accessibility score is above 7⅓/10, but neither should be booked until accessibility is checked.

Weights: cost 40%, transit 30%, accessibility 30%. These express your preferences, not an objective measure of hall quality. Scores below use only the supplied scoring scale.

Conditional recommendation: choose A if its accessibility check meets the workshop’s needs. Based on the supplied scores, A’s 8.6 exceeds B’s maximum possible 8.4; the opening threshold claim is therefore incorrect. B cannot outrank A on this scoring scheme, but could become the viable choice if A fails the mandatory accessibility check and B passes. If both fail, neither is suitable.

Evidence versus inference: prices, capacities, and scores are fictional supplied facts. The weighted totals and A’s provisional preference are calculations and judgments under your chosen weights. A 0.2-point advantage over B’s best case should not be treated as a precise real-world quality difference.

Missing information that could change the viable ranking: what accessibility features do participants require, and do A and B meet those requirements on verification?

Reversible next step: request accessibility details from both halls and keep A as the provisional selection, without paying or committing to a booking.

The combined mean score is 7, because the group of 30 people contributes three times as much to the overall average as the group of 10.

Example

A weighted mean is an average in which each value contributes according to its weight, meaning how much it counts. When combining group means, the weight is the number of people in each group, so each person counts equally.

Imagine combining the fictional scores of two groups of community volunteers:

• Group A: 10 people with mean score 4 → total score 10 × 4 = 40.
• Group B: 30 people with mean score 8 → total score 30 × 8 = 240.
• Together: 40 people and total score 280 → combined mean 280 ÷ 40 = 7.

Simply averaging the two group means, (4 + 8) ÷ 2 = 6, would give the smaller group the same influence as the larger group. Counting all 40 people equally gives 7 instead.

Boundary case

If both groups had 10 people, their weights would be equal. Then the combined mean would be (10 × 4 + 10 × 8) ÷ 20 = 6, the same as the ordinary average of the two group means.

What this does not mean

A mean of 7 does not mean everyone scored 7, or even that anyone scored exactly 7. It does not tell us how spread out the scores are or why the groups differ. The result is exact if the supplied means are exact, the groups do not overlap, and scores use the same scale. If the means were rounded, 7 would be an approximate combined mean. These fictional numbers establish no claim about real volunteers.

The workshop date, registration cap, and supply-reuse policy are decided; hall confirmation, accessibility ownership, reminder timing, and projector availability remain unresolved. This is a record of a fictional meeting, and the message below is a draft only.

Decisions

Paid social ads are a proposal, not an approved decision (N05, N12).

Action table

Dates below are in September 2026, using the meeting’s stated year.

The supply count informing reuse is an inference, not a separately agreed dependency. Projector verification needs follow-up, but the notes do not assign an action, owner, or deadline for it.

Unresolved questions

• Who will own the accessibility check due 11 September?
• When must Bo send the volunteer reminder?
• Does the hall have a working projector, and who will verify it by when?
• Has the hall been reserved and confirmed? The notes record a commitment, not completion.
• When is the next meeting, and will paid ads be approved then? No advertising spend is authorized by these notes.

Follow-up message draft

“Thanks, everyone. Our agreed workshop is 19 September 2026, 14:00–16:00, with registration capped at 24. We will reuse existing supplies before buying replacements.

Chen will count supplies by 8 September. Bo will reserve the hall by 9 September. Ada will publish the registration page by 10 September after Bo confirms the hall; publication depends on the booking.

We still need an owner for the accessibility check due 11 September, a deadline for Bo’s volunteer reminder, and confirmation of a working projector, including who will check and by when. Please also confirm the next meeting date so the paid-ad proposal can be discussed. Paid ads have not been approved.”

All versions below describe the same fictional update. “Requested action” is proposed wording for the audience, not evidence of an existing assignment. No version confirms a venue or guarantees admission.

Project sponsor

The workshop is scheduled for 19 September 2026, 14:00–16:00, with capacity for 24, an allocated budget of $180, and a need for 4 volunteers. The hall booking and projector availability remain unconfirmed. Requested action: help resolve those two open items and support filling the volunteer need. Ada owns the registration page, which is due 10 September; no deadline or owner for confirming the hall or projector is supplied. [Needs confirmation before adding a commitment: who will resolve each open item, and by when.]

Volunteers

We need 4 volunteers for the workshop on 19 September 2026, 14:00–16:00, serving up to 24 participants with an allocated budget of $180. The hall booking and projector availability remain unconfirmed. Requested action: indicate your interest and availability for the session; roles and any time needed outside the session still need confirmation. Ada owns the registration page, due 10 September; no volunteer response deadline is supplied. [Needs confirmation before adding a commitment: volunteer roles, full attendance times, response channel, and response deadline.]

Participants

The workshop is scheduled for 19 September 2026, 14:00–16:00, with capacity for 24 participants; this update does not reserve or guarantee a place. The hall booking and projector availability remain unconfirmed. Requested action: check the registration page once it is published for the registration process and venue updates. Ada owns that page, which is due 10 September; the due date is not a promise that it is already available or will definitely be live then. The workshop has an allocated budget of $180 and needs 4 volunteers. [Needs confirmation before adding a commitment: the registration link, admission process, and confirmed venue.]

Shared fact ledger

The factual statements above come only from the supplied fictional update. Audience actions are requests, not new project facts; bracketed items explicitly identify details requiring confirmation before they can be stated as commitments.

1. Prerequisites — required before collection: Have the signed inventory and an assigned pickup slot. Evidence: inventory reference and signature present; assigned slot record. If either is missing, the stated prerequisites are not met: do not start collection.
2. Count every item together with the sender. Compare each count with the inventory. Evidence: item identifier, inventory quantity, joint count and difference.
3. Photograph every damaged item. Evidence: damaged item identifier and photo reference.
4. Decision — any count difference: Stop signing and refer the discrepancy to the coordinator. The coordinator must reconcile it before signing resumes. Evidence: discrepancy, referral, coordinator's reconciliation and outcome. Do not treat referral alone as reconciliation.
5. When there is no difference, both receiver and sender sign. For a discrepancy case, sign only after the coordinator has reconciled it. Evidence: both signatures and, where applicable, the reconciliation record.
6. Receiver stores one copy; sender stores another. Evidence: receiver copy location and sender copy location or storage confirmation.
7. Transport stop — damaged electrical items must not be transported. Evidence: affected item identifiers, damage photo references and a record that those items were not transported. This restriction still applies when counts match and signatures are complete.

Decision tree in prose: Before collection, check the signed inventory and pickup slot. If either is absent, collection cannot begin. Otherwise count with the sender, compare with the inventory and photograph damage. If counts differ, stop signing, refer to the coordinator and wait for reconciliation before signing. If counts match, both sign. Retain one copy each. Independently of the count decision, do not transport damaged electrical items.

Helpful suggestion: A colored folder may make the copies easier to find. It is optional; no evidence of folder color is required.

Evidence record fields: inventory reference; prerequisite signature present; assigned pickup slot; receiver and sender identifiers; item identifier; inventory quantity; joint count; difference; damage description; photograph reference; coordinator referral; reconciliation and outcome; receiver signature; sender signature; receiver copy location; sender copy location/confirmation; damaged electrical item not transported.

These fields organize evidence for the stated controls; the procedure does not specify a form, retention period, who signs the prerequisite inventory, the reconciliation method, or disposal/repair arrangements. Do not invent those requirements.

All evidence below is fictional training material. Confidence describes what each source supports, not independent verification of a real event. Supporting passages are precise paraphrases, not quotations.

Registration was announced for 12 September, but its actual opening cannot be established: S2's 11 September report may involve rehearsal and has an unresolved publication/event chronology. Eligibility outside the local community was undecided, and no complete eligibility policy is supplied. Evening interest appears in one interview, but evening demand is not established. None of these gaps should be silently resolved.

The six synthetic interviews (I01–I06) are a directional, nonrepresentative sample. Counts below describe only these notes. Themes overlap and must not be added together as unique participants.

Counterexamples: I02 directly challenges an evening-only choice; I01 challenges a morning-only choice. I06 challenges treating time as every participant's main concern. I03 shows that an evening preference can coexist with a transport barrier. I04 and I05 show that accessibility cannot be assigned to just one time slot.

Opportunity hypotheses, not established solutions:

• Offering a choice of morning and evening sessions may accommodate the conflicting constraints in I01 and I02; validate demand and operational feasibility before choosing two sessions.
• Aligning an evening session with usable bus times may help I03; verify the actual journey and return trip.
• A wheelchair-accessible venue and clear access information may support I04 and I05; confirm the specific access requirements and venue conditions.
• Free admission may remove a priority concern for I06; check whether that matters to other participants and whether funding permits it.

Follow-up questions:

1. For I01–I06, which exact dates and start/end times are possible, preferred or impossible?
2. For I02, would a different evening time help, or is evening attendance unavailable regardless of timing?
3. For I03, which route, journey times and last return service constrain attendance? Is any workaround already used?
4. For I04 and I05, what entrance, circulation, seating and toilet access is required, and what needs checking at the proposed venue?
5. For I06 and then the others, would a charge prevent attendance, and are transport or other costs also relevant?
6. Across a broader recruited sample, do these themes recur? Record recruitment and nonresponses before interpreting demand.

Both editors can meet the requirement to edit Markdown on macOS and Windows without a mandatory paid AI subscription. My conditional recommendation is VS Code for a group that wants a documented built-in Markdown preview; Zed is also a viable free-editor candidate, subject to a device and document trial.

Access and price snapshot: 2026-09-07 UTC. Region: user's country unspecified; this comparison uses the public English-language sites, not a verified country-specific checkout. Zed displays dollar prices; currency code, local taxes and regional eligibility were not established by the retrieved page. Prices and allowances may change.

Evidence notes: I read the requested Zed documentation landing page and pricing page, then the linked platform and Markdown pages. The requested VS Code setup URL redirects to the cited Get started page. The requested VS Code FAQ timed out twice, so I have not claimed to verify its contents. All linked pages above were accessed on 2026-09-07; these are documentation observations, not hands-on performance measurements.

Unknowns that matter before adopting a policy: exact VS Code OS/hardware support for the group's machines (official system requirements); Zed's minimum Windows version (installation requirements); current Copilot numerical limits and paid pricing (GitHub's official Copilot plans); Zed prediction reset period (plans/billing documentation); and country-specific AI availability, currency and tax treatment (vendor terms and regional billing information). No nonprofit discount or special eligibility was verified. Zed's listed trial does not substitute for enduring free core access, and own-key usage does not eliminate provider costs.

If the priority is straightforward Markdown editing and preview with no AI budget, start with VS Code and leave optional AI unused. If the group prefers Zed's interface, test representative Markdown files on one Mac and one Windows machine, especially whitespace preservation and preview needs, before standardizing. The sources establish viable access paths; they do not establish which interface your volunteers find easier. No purchase was made.

1. [P1] Divide the percentage by 100 before applying it — src/tickets.ts:2. The contract supplies a value from 0 to 100, but the expression treats it as a fraction. For 1,000 cents at 20%, it returns −19,000 cents instead of 800; at 1%, it returns zero. This breaks ordinary pricing inputs and can produce negative prices. Change the expression to Math.round(cents * (1 - percent / 100)), subject to confirming the rounding rule below.

2. [P1] Sort a copy to preserve the caller's array — src/tickets.ts:5. Array.prototype.sort reorders items in place and returns that same array. Calling this with [200, 100] changes the caller's sequence to [100, 200], directly violating the explicit ownership contract and potentially changing other displays or processing that share it. Use [...items].sort((a, b) => a.cents - b.cents). A shallow array copy is enough to prevent this sort from reordering the original; it does not promise independent item objects.

Questions to resolve from the surrounding contract, not assumed defects:

• What rounding rule applies to fractional-cent discount results? Whole-cent output does not specify nearest versus floor/ceiling or tie handling.
• Are nonfinite numbers, negative prices, fractional percentages and values outside 0–100 rejected by callers or by these functions? The diff does not establish validation responsibility.
• What maximum cents value is supported? JavaScript number precision may matter at large values, but no such input range is supplied.
• Are returned objects intended to be shared with the input, or does the API promise a deep copy? Only preservation of the original array is stated.

Focused verification plan:

• Discount boundaries: discountedCents(1000, 0) === 1000, (1000, 100) === 0, (1000, 20) === 800, (1000, 1) === 990, and zero cents at valid discounts remains zero.
• Add fractional-cent cases after agreeing the rounding rule; for nearest-cent rounding, (101, 50) === 51.
• For [a:{cents:200}, b:{cents:100}], assert ascending result [b,a], original order still [a,b], and result array is a different reference. Repeat with a frozen input array to expose accidental mutation.
• Cover empty, single-item and equal-price arrays. Check any explicit tie-order requirement if one exists.
• Run the repository's existing type check and tests, then examine call sites for discount validation, pricing expectations and array ownership. No tests or call-site inspection were performed from this supplied diff; no security exploit or actual data loss is established.