A scoped-evidence packet

A contribution,
in context.

Show one piece of work. Say what it supports—and what it doesn’t.

Use a short packet in your existing website or email workflow. A reference is optional. There’s no need to join a network or rebuild a portfolio; stop if your website and email already do the job.

Read the worked example Download the blank kit (.txt)

01 / For an existing website

The work.
Not an endorsement.

An invented repair handoff checklist. The excerpt makes update responsibility, timing and a fallback inspectable; it does not demonstrate improved repair outcomes.

The destination is a fictional page title, not a live work URL. The website version omits the private brief and referee. No reference is a valid finished packet.

Complete fictional website packet

Scroll inside the read-only text to read the whole block. To copy, focus it and select all (Ctrl+A or ⌘A). On mobile, use text selection or the plain-text download. Keep the fiction label and boundary.

FICTIONAL WORKED EXAMPLE — NOT REAL WORK OR A REFERENCE
WORK / CONTRIBUTION PACKET
Packet version and prepared date: 1; 2026-09-30
Intended use: DRAFT — NOT FOR SHARING
Proposed destination: fictional portfolio page “Repair handoff checklist” only

WORK
Title and work version/date: Repair handoff checklist; v1, 2026-09-30
Existing permitted source: no external source; invented excerpt reproduced below
My contribution (fictional): I drafted the next-update fields and the escalation
prompt. I did not run a service trial or design the repair team's whole workflow.
Inspectable evidence — entire invented blank checklist excerpt:
  Repair case: [leave blank in this example]
  Next update owner: [role responsible for the next customer update]
  Update due: [date and time agreed by the team]
  If the owner is unavailable: [escalation role and handoff action]
What this supports: the draft makes update responsibility, timing and a fallback
explicit enough to discuss with an operations lead.
What it does NOT establish: use by any team, fewer missed updates, improved
repair outcomes, research competence or ownership of collaborators' work.
Sharing basis: invented rehearsal content only; no real client material or approval.

REFERENCE — OPTIONAL
Status: NO REFERENCE SHARED

BOUNDARY
Fictional preparation material, not independently verified evidence. No identity,
authorship, competence or procurement approval is implied. No actual permission
is recorded. A real public page needs its own destination-specific rights review;
private referee permission cannot be transferred to it. Copies may persist after
correction or withdrawal; an old copy would not prove current referee support.

Download website example (.txt)

02 / For an existing email workflow

One useful
next question.

The same evidence, an invented brief and one question about who would own a trial. Fees, travel funding and commissioning authority remain unknown—not agreed terms.

This is a self-contained rehearsal, not an instruction or link to send anything. It contains no real address and no reference.

Complete fictional email packet

Scroll inside the text to read the whole block. Select all and copy, or download the plain text. Keep “do not send,” the limits and the boundary in your rehearsal copy.

Subject: FICTIONAL REHEARSAL — handoff trial scope question

FICTIONAL WORKED EXAMPLE — DO NOT SEND
Packet v1, 2026-09-30. DRAFT — NOT FOR SHARING.
Proposed destination: fictional commissioning lead at Harbour Repairs only.
Proposed purpose: explore fictional brief A, a two-week handoff-checklist trial.

For brief A, my invented “Repair handoff checklist” v1 (2026-09-30) may be relevant.
There is no external source or real client evidence. The full invented excerpt is:
  Repair case: [leave blank in this example]
  Next update owner: [role responsible for the next customer update]
  Update due: [date and time agreed by the team]
  If the owner is unavailable: [escalation role and handoff action]

My fictional contribution was drafting the next-update fields and escalation
prompt, not running a trial or designing the whole workflow. This supports a
discussion about responsibility and fallback; it does not establish actual use,
fewer missed updates, improved repair outcomes or research competence.
Sharing basis: invented rehearsal content, not real permission or client material.

REFERENCE — OPTIONAL
Status: NO REFERENCE SHARED

One next question: Which operations role would own testing the fallback handoff
when the usual update owner is unavailable?
Decision the answer changes: with an authorised trial owner, explore a bounded
checklist trial; without one, decline this scope rather than promise implementation.
No-go condition: no authorised trial owner, or a requirement to guarantee improved
repair outcomes from this untested checklist.

Terms to confirm: two weeks is a proposed duration only. Availability, working
days, remote/on-site needs, travel funding, fee/day rate, GST/tax treatment,
expenses and commissioning/budget authority are all unknown, not agreed.

BOUNDARY
Entirely fictional preparation material, not independently verified. No scoped
reference, general endorsement, identity/authorship check or procurement approval
is provided. A real packet would be limited to its reviewed destination and
purpose; ask before further sharing. Copies can persist after correction or
withdrawal; recheck current permission and scope before relying on older copies.
This is an exploratory question, not an application, appointment or commitment.
The recipient's existing commissioning process would still apply.

Download email example (.txt)

03 / Separate from the packet

Ask for permission.
Don’t assume it.

The optional request proposes a named-recipient use only, never website publication. No reply or endorsement is invented. These are requested limits, not permission granted.

A real request needs separate authority to contact the referee through an independently established route. This page authorises no outreach, recruitment or personal-data collection.

Read the fictional permission request

Complete fictional request—not a reference

Keep this separate from the outgoing packet. Scroll inside the text to read the whole request. Select all and copy only for a fictional rehearsal.

Subject: FICTIONAL REHEARSAL — optional reference request for checklist v1

FICTIONAL DRAFT — DO NOT SEND; NO PERMISSION OR STATEMENT EXISTS
To: fictional delivery colleague (no real contact details)

Would you be comfortable describing only what you directly observed of my
next-update fields and escalation prompt in Repair handoff checklist v1,
dated 2026-09-30? Please correct the contribution description if needed.
The proposed excerpt consists only of the blank repair-case, next-update-owner,
update-due and unavailable-owner fallback fields, not client records.

Proposed destination: the fictional Harbour Repairs commissioning lead only.
Proposed purpose: evaluate my contribution for fictional trial brief A only.
Proposed restrictions: no onward forwarding, no website publication, no reuse
for brief B or a changed checklist. Proposed expiry: 2026-10-31.
These are requested limits, not permission already granted.

If willing, please write your own statement, working relationship, what you
directly observed, what you cannot attest to, and attribution you permit.
Separately confirm whether that exact statement may be shared for the named
recipient and purpose above, with the restrictions and expiry, or specify narrower
limits. No permission is the default, including no reply. Declining or correcting
has no penalty and says nothing about performance.

You may ask for correction or withdrawal through this established route. I can
remove a statement from copies I control and ask known recipients to stop relying
on it, but cannot erase emails, downloads, backups or caches held by others.

Download fictional request (.txt)

No reply means no permission. Pending permission or refusal means no reference shared. Refusal or correction carries no penalty and says nothing about performance.

Before real use

Permission belongs
to a destination.

Private approval is not public consent.
Public approval is not email consent.

Use the blank kit for real work, not the fictional example. Prepare privately and review the whole outgoing packet: exact work version, rights, recipient or exact public page, purpose, current permission and all restrictions. A public URL alone is not copying permission. If permission or privacy is unresolved, omit the affected material or do not share.

Keep the scope intact

Named-recipient approval for brief A does not permit a website, forwarding or brief B. Include the complete approved reference section and boundary, not an isolated endorsement: exact words, attribution, observation, relationship, scope, limits, destination, purpose, restrictions and dates. Never generate praise for the referee.

Check again when things change

Changed work or purpose, expiry, withdrawal or uncertain permission means no current reference shared. Remove the statement and attribution from copies you control and future packets; notify known prior recipients not to rely on or reuse it. Fresh use needs fresh permission.

Don’t promise control over copies

Websites and email do not enforce confidentiality. Downloads, inboxes, backups and caches may persist. A packet cannot authenticate a referee, prove authorship, enforce restrictions or recall copies. If the copying risk is unacceptable, do not share.

Start with your own
permitted work.

The blank kit includes the packet, safety review, reference-status rules and optional request and email templates. Edit it only in your own approved private workflow. For a public work page, omit the private brief, contract section, private reference and contact details. No reference is required.

Download the blank kit (.txt)

This is a working aid, not a verified reference or validated product. The synthetic study is not participant evidence; issue #6 and the empirical gates remain open. Demand, adoption, hiring value and preference over existing website/email workflows are unproven. No live pilot is authorised.

A contribution,in context.

The work.Not an endorsement.

One usefulnext question.

Ask for permission.Don’t assume it.

Permission belongsto a destination.