Effort is not a promised result.

The reusable decision

Use this policy as a review aid; do not automatically assign the extracted tasks. A promise to try requires effort-only wording. A start date belongs in the task, not the deadline field. General requests and useful suggestions remain outside a commitments-only register unless accepted. The final register contains four historical action rows across two excerpts; four other excerpts correctly remain empty under the stated policy.

These are agent task choices, not a universal interpretation of meeting language. Some teams exclude tentative commitments entirely or track requests separately. Agree on that distinction first. A null owner means no explicitly named owner was established; it is not permission to assign the speaker. Dates here describe 2019 intent, not work still outstanding today.

See this recommendation saved with its exact evidence in a separate format-6 project. The original exercise downloads remain unchanged.

What changed after review

Both authored sets pass structure on all six cases. The first pass passes expected fields on two cases but only one is self-accepted. R01 is the important gap: its owner, ID and deadline all pass while its task exaggerates the promise. The revised set passes expected fields and is self-accepted on all six. There are six paired cases, but these counts describe an editorial exercise—not accuracy estimates or causal prompt comparisons.

The revision supplements the existing commitment policy rather than silently changing the original fictional pack. Exact refinements:

Historical-source scope: evaluate what is explicitly open in the excerpt at the time of that meeting, not what remains open today. Do not use a linked discussion or today's date to fill gaps. A commitment to try promises effort, not successful completion: preserve that qualification. Explicit commitments by several individually named people are separate actions and may share the same source_id. A collective plan explicitly adopted in the supplied context can be an action, but a collective pronoun does not establish a named owner. Preserve a stated start date in the task; it is not a due date unless the note also states a deadline. A general request to read, a wish for a guide or a suggestion to collect a list is not an accepted assignment. Source metadata and license notices are not meeting notes.

R05 also needs the preceding settled-arrangement paragraph to resolve “this idea”. It is supplied verbatim in both variants; the revision does not get extra source evidence. No linked discussion was used to fill a gap.

Reproduce, inspect, adapt

1. Read the source excerpts and the policy disagreements above. Download the provenance manifest with exact quotations, context, SHA-256 hashes and pinned source URLs.
2. Download the unrun project or preview it in the Test Bench. It has no responses or judgments. Both variants see exactly the same source input. The B policy is intentionally informed by this exercise: use unseen notes for any later evaluation.
3. Run prompts with your own model or chat tool. PromptKB itself makes no model call. Expected records and review notes are not in the rendered prompts; source attribution and the license notice are.
4. Review source grounding and scope, not just checks. Use the full Markdown report and script-free HTML handoff to inspect the authored example without importing it.
5. Download the historical reading register only as a scoped reading aid, not a live assignment system. Keep its sources and license with it.

Projects use format 5 for structure contracts. The browser stores nothing unless you enable Remember; starter loading replaces only the current tab after confirmation. Download current work first. Attribution travels in each case input because the current project format has no separate source metadata fields; that increases prompt length but keeps standalone files attributed. Do not strip the included license when redistributing excerpts.

Sources and permission

Excerpts from Rust compiler-team steering-meeting minutes, by the Rust compiler-team contributors. Repository MIT permission notice is included unchanged. No affiliation, endorsement or current assignment is implied. The upstream README reports that its website was retired in April 2025; these are historical repository documents, not current team policy.

Each quote is an exact contiguous Markdown excerpt from a pinned source file. N1 labels, source metadata, task policy, expected fields, responses and review notes are PromptKB agent additions. Evaluate the excerpt at its stated historical meeting time, not as a claim about work still outstanding today. Linked discussions are outside this exercise and were not used to fill gaps. The six selections are not the complete meetings, a representative dataset or independently reviewed ground truth.

Pinned commit: 6cf981d16c1852074b397eee544adc3d1a7eb6b6. Retrieved 2026-11-03T22:06:29Z. Upstream README · Unchanged MIT notice.

PromptKB's added prompts, expected fields, authored responses and review commentary may be reused and adapted, including commercially, without attribution, as-is without warranties. That grant does not replace the upstream MIT conditions on source excerpts. Source hashes identify the downloaded bytes; they do not authenticate the truth or completeness of the minutes.

Permission is hereby granted, free of charge, to any
person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the
Software without restriction, including without
limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following
conditions:

The above copyright notice and this permission notice
shall be included in all copies or substantial portions
of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Original fictional action-register pack · What structure checks can and cannot establish