Build a fieldwork portfolio

Completed demonstration portfolio — Weekly Fieldwork

Portfolio register

- Week 1: Completed observation record — conservatory; record and transfer included below. - Week 2: Completed recall strategy — storm kit; record and transfer included below. - Week 3: Completed spatial model — dome connector; record and transfer included below. - Week 4: Completed mechanism diagnosis — conservatory lift; record and transfer included below. - Week 5: Completed example — beacon with two faults; record and changed-condition reasoning included below. - Week 6: Completed example — request authority and repaired weather ledger; record and changed-condition reasoning included below. - Week 7: The embargoed observatory charter — completed record; record and changed-condition reasoning included below. - Week 8: Five cases to the dome — completed record; record and transfer included below. - Week 9: The council that changes its brief — completed record; record and changed-condition reasoning included below. - Week 10: Predict the instrumented gallery — completed record; record and transfer included below. - Week 11: When the release authority expires — completed record; record and changed-condition reasoning included below. - Week 12: Recover the rainfall recorder — completed record; record and transfer included below.

Completed demonstration example — conservatory observation record

Initial inspection

At the first inspection the clock displayed 11:35, a green mug stood beside the planting ledger and the service hatch was closed. These are supplied scene observations. A visible note asserted, “I checked every tray.” The note's presence is observable; its contents remain a claim.

Reconstruction and correction

I initially recalled the hatch as open. Rechecking the scene showed that I had inserted a familiar detail. I preserved the incorrect recollection and correction rather than rewriting the attempt. I classified “the tray inspection lasted thirty-five minutes” as an inference: the 11:35 reading alone supplies neither the inspection start nor its duration.

Changed situation

At the second inspection the clock read 11:50 and the hatch was open. The green mug remained unchanged. Two recorded features changed. No record established who opened the hatch or why.

Next investigation

Inspect the tray check records against the claimed complete inspection. Matching records would support the account within their scope; missing entries would require clarification.

Reflection

My main error was adding a plausible detail, not failing to look at an object. A regional inspection helped coverage, but preserving a separate interpretation column helped more with this mistake. In my own scene I would make the same distinction before building a story. I would not claim that two changed features prove a particular person's intent.

Further reflection

Completed demonstration example — storm-kit recall strategy

Baseline

I recalled Lens and Beacon: two correct items out of four. I kept that result before inspecting the full list.

Encoding route

1. Gate: a giant Lens frames the entrance. 2. Pool: a Tether splashes in the water. 3. Press: a Pocket atlas unfolds into maps under the rollers. 4. Dome: a Beacon lights the roof.

Retrieval and error

With the list covered, I retrieved Lens, Tether, Pocket atlas and Beacon in order. A later attempt produced “book” at the Press. I recorded the substitution and strengthened the map-specific cue rather than silently counting it as exact recall.

Comparison

The guided attempt improved from two correct items to four. That is a result of this small demonstration, not proof of permanent improvement or photographic memory. Rehearsal and item familiarity may also have helped.

Reflection

The fixed locations helped order, while the distinctive images helped item identity. The delayed substitution showed that a generic association preserved a category but not the required object. In another task I would preserve the route, change the items, and inspect whether the same weakness returned. For a critical instruction set that can be carried openly, a checklist may remain the better tool.

Further reflection

Completed demonstration example — dome connector

Reference frame and prediction

World north and up remain fixed when the camera moves. The alternate connector initially has north/west ports at level 0. A clockwise 90-degree turn maps the original north port to east and the original west port to north.

Transformation record

- Initial: 0 degrees, level 0, north/west. - After rotation: 90 degrees, level 0, east/north. - After translation: 90 degrees, level 2, east/north. - Verification: both labelled ports and the required level match.

Changed destination

The target moved to level 1 without changing port requirements. I lowered the connector and retained its 90-degree orientation.

Reflection

I initially treated reaching the right orientation as completion, but the target included a separate height condition. Writing two checks prevented that omission. Tracking the original north tip also made the rotation explainable when the camera changed. In a new configuration I would predict the label mapping before movement and then test position independently.

Further reflection

Completed demonstration example — conservatory lift

Causal model

Input rotation → external gear pair → cam → spring-return follower → lift output. The interlock blocks cam adjustment until released. Motion also requires the spring and specified cam phase.

Prediction and diagnosis

For three output turns from five input turns: follower = 18 × 5 ÷ 3 = 30 teeth. The driven gear turns opposite the driver. A correct ratio did not initially produce a ready mechanism because the interlock was engaged and the return spring absent.

Verification

Five input turns produced three opposite output turns. Both the amount and direction matched the prediction.

Transfer

The changed task required two output turns from four input turns. I selected 36 follower teeth: 18 ÷ 36 × 4 = 2. The cam and spring conditions remained valid.

Reflection

The useful distinction was between an incorrect transmission ratio and a blocked dependency. Changing gears would not have released the cam. In a new apparatus I would record the output requirement, list readiness conditions and test both separately.

Further reflection

Completed demonstration example — beacon with two faults

Initial evidence and first diagnosis

With power on, source / fuse output / cable output / lamp supply read 9 / 9 / 0 / 0 V relative to the common return. The lamp was dark. The first missing supply supported an open cable. The unpowered lamp's own condition remained unresolved; the readings did not prove it healthy.

First repair and failed whole-system check

I isolated the source and replaced the cable only. After restoring power, the trace became 9 / 9 / 9 / 9 V, but the same beacon stayed dark. The repair successfully restored supply without resolving the original symptom. I preserved both statements instead of calling the cable diagnosis wrong or declaring the job complete.

Second diagnosis and repair

With healthy supply and a dark load, I isolated power and tested lamp continuity. The result was open. I replaced that confirmed open lamp while isolated, then restored power. The supply remained 9 / 9 / 9 / 9 V and the lamp lit.

Preserved diagnostic chain

Reflection

My first diagnosis was useful but incomplete. Assuming it explained the entire symptom would have stopped the investigation too early. The failed output check changed what I needed to test, without erasing the evidence that justified the cable replacement. In a new case I would read whether its rules permit multiple faults, diagnose from its own trace and check the original symptom after every repair. This example does not establish that the assigned one-fault circuit has two defects.

Limits

These are idealised authored model readings, not measurements from constructed hardware. A continuity check is performed only in the model's isolated state. The record establishes this fictional apparatus's behaviour and does not certify work on an arbitrary physical circuit.

Method to carry forward

Further reflection

Completed demonstration example — request authority and repaired weather ledger

Published authority rule

Only an instruction marked authenticated in the supplied authority register can supersede the current request. This is a fictional case-file rule; no live signature service is contacted.

Preserved timeline

Preserved recommendations

1. Under R1: select North after count and digest checks. Its newer timestamp neither proves nor disproves correctness. 2. After the unsigned message: retain North as the currently authorised deliverable. Preserve the request, ask for authenticated authority and do not quietly promote the claim into a rule. 3. Under authenticated R2: select South S2, after separately checking authentication, 18 sections and Q-12. Preserve the original South record at 17/Q-2 and the original North justification.

Two independent checks

Authentication established what the current instruction required. The repair receipt and new comparison established what South S2 contained. Neither check could substitute for the other. The old incomplete South file was not silently rewritten into a successful historical result.

Limits and next check

Agreement with the authenticated reference establishes identity and completeness within this case. It does not prove the scientific accuracy of the weather observations. The unsigned Q-9 proposal remains an unverified account; the later R2 does not retroactively authorise it. Its origin and purpose would need separate investigation.

Reflection

I initially expected a later request to trigger a different selection. The authority rule showed why keeping North at 08:00 was the justified action. When an authenticated instruction and a newly repaired record later appeared, I changed to South S2 for two explicit reasons. The useful method is to verify authority and content, not to memorise “choose the first copy, then the second.” My assigned case has different rules and records, so I must read those afresh.

Method to carry forward

Further reflection

Completed demonstration example — embargoed observatory permission audit

Published authority

Reader: read research only. Maintainer: service equipment only; embargoed research is not readable. Custodian: read research and approve release. Every other combination is denied.

Preserved faulty results

| Request | Expected | Observed before repair | | --- | --- | --- | | Maintainer / read | Deny | Allow | | Reader / read | Allow | Deny |

Version 1 — repaired charter

| Role | Read | Service | Approve | | --- | --- | --- | --- | | Reader | Allow | Deny | Deny | | Maintainer | Deny | Allow | Deny | | Custodian | Allow | Deny | Allow |

Version 2 — new release hold

A later signed notice suspended custodian approval. The other eight decisions stayed as in Version 1. Reader and custodian could still read; maintainer could still service but could not read research. The previous correct approval is preserved under its earlier authority.

Reflection

I initially expected equipment responsibility to include research visibility. The embargo contradicted that shortcut. Checking forbidden operations alone would also have missed the blocked reader, so I recorded both kinds of failure. The release hold was a new rule, not proof that the original approval test was dishonest. In the assigned lab I must derive a fresh table from its own charter and identify exactly which right its later notice changes. I can reuse the testing method without reusing these permission answers.

Method to carry forward

Further reflection

Completed demonstration example — dome handoff

Role information

Analyst card: five sealed cases to Dome, verification VIOLET. Operator: controls dispatch and must request exact destination, count and code.

Recorded exchange

Analyst: “Deliver five sealed cases to Dome; verification code VIOLET. Read back before dispatch.” Operator first read-back: “Dome, four, VIOLET.” Analyst: “Correct the count to five.” Operator corrected read-back: “Dome, five, VIOLET.” Analyst: “Confirmed.”

Changed situation

New card: Pool / 2 / SILVER. The team repeated the same protocol with new values. The operator's matching read-back was confirmed separately from the earlier handoff.

Agreement

The analyst owns instruction accuracy; the operator records and repeats the three fields; either role may stop if a field conflicts. A completed acknowledgement applies to one identified instruction, not every later delivery.

Reflection

The protocol was useful because it made the receiver's interpretation visible. My error was a wrong count, not unwillingness to cooperate. In another task I would preserve exact labels and ask which condition permits action, especially when the roles see different screens.

Further reflection

Completed demonstration example — changing-brief council agreement

Responsibilities and original authority

Ada is the caretaker. Rin compares the record copies. Bo checks transport capacity. The mediator coordinates the agreement. Recipient Mira initially needs the physical ledger for a provenance examination; Ada authorises that handover if custody and return are recorded.

Claim and capacity checks

Rin claims the supplied copies have matching recorded content. Cedar and Birch each contain twelve sections with digest R-4. The record corroborates that limited claim; it does not prove the observations scientifically true or establish Rin’s intent.

Agreement Version 1 — prepared, not executed

Send the original to named recipient Mira using the certified cart, record custody with Ada and retain the return commitment. Copy-only delivery would not meet the physical provenance request. No dispatch occurs before the next notice.

Replacement brief and Agreement Version 2

The replacement signed brief cancels physical examination before dispatch. Mira now needs remote catalogue access; the original must remain with Ada. Transfer the verified Cedar copy, record the reference used and confirm the recipient’s access. The 9-unit cart remains usable but is no longer needed. The original stays with Ada.

Reflection and limit

I checked the claim even though it turned out to be supported. I did not infer honesty or deceit from the speaker’s manner. The adequate cart made the first physical agreement feasible, but it did not entitle me to ignore the later instruction. The change was in the requested outcome, not a new equipment failure. Preserving the unexecuted first agreement made that distinction visible. In the assigned council I must reread its comparison records, capacity certificate and current mandate instead of copying this physical-then-copy sequence.

Method to carry forward

Further reflection

Completed demonstration example — instrumented gallery routes

Original sensor set

15, 16, 11.

Changed sensor set

21, 22, 23. Route B now records three contacts; Route A records zero. The earlier records remain labelled with the original pattern.

Decision

If the objective is minimal recorded contact, Route B fits the original pattern and Route A fits the changed one. If the task is to verify detector observations, a route through the sensor cells may be more useful. Contact is a game event, not automatic failure.

Reflection

The most useful artefact was the ordered route plus the sensor set, because it made each count reproducible. I avoided treating a once-correct zero as a permanent property of the path. In my own task I would predict before execution and inspect the first disagreement rather than changing the route until an attractive ending appears.

Further reflection

Completed demonstration example — release-authority revision memo

Version 1 and its authority

Verify ledger → Seal case → Dispatch case → Log receipt.

Published disruption

The replacement notice withdraws the old dispatch authority. Before sealing, the investigator must compare the recipient’s request with this ledger’s identity and purpose. The coordinator must record the new authorisation. Neither open routes nor working equipment removes those conditions.

Diagnosis and retained evidence

The failed dependency is the old authority to seal and dispatch. The unchanged signed ledger comparison remains useful for identity. Equipment remains available. Neither finding establishes that the recipient’s current request covers this ledger. No route change is required.

Version 2

Verify ledger → Check recipient scope → Record new authorisation → Seal case → Dispatch case → Log receipt.

Communication and status

The coordinator reads back the new order and stop condition; all roles acknowledge them. Version 1 stays preserved. This memo records a revised plan, not an invented completed authorisation or dispatch.

Reflection

My first temptation was to choose another route, but availability was not the dependency the notice changed. The important change was the point at which permission had to be established. Adding a scope check after dispatch would mention the new rule without satisfying it. I kept the identity evidence, named an investigator to check scope, and made the coordinator receive and record the result before sealing. In the assigned route or meter disruptions I must identify their different failed dependency instead of copying this sequence.

Method to carry forward

Further reflection

Completed demonstration example — Lark Weather Mast recovery

Mission contract

Recover verified rainfall data while keeping the original recorder stable. Abort movement if the support apparatus cannot meet its required output. The original remains with the mast custodian.

Evidence and actions

The display read 16:25 and the service lamp was amber. The operator's completeness statement remained a claim until the manifest check.

Resolution

Verified digital data recovered; original stabilised in place; receipt and custody recorded.

Alternative and limit

Physical removal was unnecessary for the research-access objective and would introduce handling work. Matching W-6 establishes identity against the reference, not calibration accuracy. A calibration review remains the next question.

Reflection

The operation worked because several modest checks connected: observation informed investigation, mechanical verification supported handling, and a clear agreement defined what recovery meant. I would not describe this as physical recovery or as proof that every rainfall measurement is correct.

Further reflection

Attribution and completeness

All twelve records are labelled alternate demonstration material. Each retains its setting, supplied result, changed-situation response and reflection. A submitted personal portfolio would replace these with the student's own attempts and declared assistance. Exporting this example does not submit it.

Method to carry forward