The method behind this example
Derive expected permissions from a charter before testing observed behaviour.
Your independent challenge: The assigned role policy grants different read rights. Copying this completed matrix would apply the wrong authority.
The investigated explanation and learning record complete this example. The scene delivery is an optional extension.
Start this worked example
- Choose Watch the worked example. The student demonstrator explains the task, talks through each action, then reviews the observations and finished submission. Narration starts with this click; Mute narration keeps the same experience captioned.
- Choose Take control to try the current chapter. Follow its prompt, change the labelled controls and select Test my decision.
- Read the feedback, retry if needed, then continue with Next chapter. Each checked chapter provides evidence for one connected operation.
- After every chapter check, return to the mission station, perform the intervention, collect its package and follow the marked checkpoints to complete the handover. Watching performs these same actions with narration. Direct chapter access is a partial preview until the full evidence and handover are complete.
- Use Fullscreen mission after opening the scene to keep the instructions, chapter controls and equipment together. Reflections and exports come after your practical attempt.
This is an alternate example, not your assigned exercise. Your course task is linked after the player.
YOUR SKILL
Permission diagnosis
A NEW SETTING
A telescope console separates research-reading authority from equipment-maintenance authority.
WHAT CHANGES
This local charter permits equipment maintenance without research reading and contains two opposite permission faults. Derive the matrix from this embargo charter, then derive a fresh matrix from your assigned task's own rules.
Scene guide · people, evidence and object placement
Who the embargo roles represent
A local telescope charter separates research reading from equipment service.
- Your part
- Watch follows a worked solution. Take control lets you move the student avatar and try its decisions. The demonstrator in the explanation is modelling a solution, not an extra witness in the story.
- Your instructor
- Mara stands in the marked teaching bay outside the investigation area. She guides the exercise. Her presence, appearance and idle gestures are not clues about what happened in the case.
- People in this scenario
- Reader, maintainer and custodian are policy identities, not the visible learner or instructor. Maintainers have a specific research-reading restriction in this example.
- What counts as evidence
- Use the embargo charter, observed faulty table and later release hold. The maintainer’s equipment role does not imply permission to read research.
- Why the objects are here
- The matrix represents nine role/action decisions. Its labels and charter define authority; character appearance or location does not.
Digital Observatory
Watch the complete alternate example. Take control of the equipment whenever you are ready.
An alternate example · separate from your assessed workHow to move, inspect and complete the activity
Use WASD or arrow keys to walk. Press E near an instrument to examine it. Inspect means read its details; Use equipment performs the action named in its status message. The task controls let you choose exact settings and test a solution. Once verified, use the mission station to put it into effect, collect the resulting evidence or cargo, follow its checkpoints and complete the handover at the receiving station.
Scroll over the scene or use Zoom + / Zoom − for a closer or wider view. Click and drag to turn whenever the cursor is free. Choose Fullscreen mission to keep the scene, mission instructions and all task controls together. Fullscreen starts with a free cursor so you can scroll the panel and choose options. Press X or Lock cursor (X) to turn by moving the mouse. Press X again to free the cursor and return to click-and-drag turning. Tab also frees the cursor. The X shortcut stays inactive while typing or choosing a form value. Press Escape or Exit fullscreen to return to the page. On touchscreens, drag to look and use the zoom buttons. If your browser cannot enter native fullscreen, the mission expands to fill its window.
Choose Watch to follow the worked example, or Take control to try it yourself. The transcript and completed example remain available if 3D is unavailable. Demonstrations never change assessed progress.
I must repair the observatory’s embargo charter. Maintainers may service equipment but may not read research. I will preserve an excessive permission and a missing required permission, repair the two cells, retest the complete matrix and then apply a narrow release hold. My audit must distinguish a bug from a later authorised change. The method we are practising is: Derive expected permissions from a charter before testing observed behaviour.. Our field objective is: Restore the telescope console permissions while preserving its embargo approval rule. Repairing the reader and custodian faults must not erase the hold or maintainer responsibilities. The investigation and explained record complete this lesson. A scene delivery is an optional extension. You can pause, mute, replay, or take control at any point. The captions show the same explanation.
Narration starts after you choose Watch or Play. Captions remain available if this browser has no working voice.
Optional scene extension
Each chapter provides evidence for this operation. Inspect, investigate, act, and complete the handover.
FIELD OPERATION · Briefing
Operation Observatory Charter
Restore the telescope console permissions while preserving its embargo approval rule.
Repairing the reader and custodian faults must not erase the hold or maintainer responsibilities.
Inspect the mission station to begin your investigation.
Nothing collected.
Mission actions become available when the activity loads.
Mission record and accessible controls
These controls perform the same actions as the marked stations in the scene. Use them with a keyboard or touch, or when graphics are unavailable. Equipment tests establish whether your intervention is supported. The final handover records a mission outcome; your explanation is assessed separately.
- No mission actions yet.
The complete transcript and finished example are available below while the player loads.
THE DEMONSTRATOR’S REASONING
Derive rights from this charter
The research embargo separates two responsibilities. Readers may read research; maintainers may service equipment but may not read research; custodians may read and approve release. Every other combination is denied. A job title does not imply extra access.
Why this matters
Equipment responsibility and research visibility are separate permissions in this local model.
A plausible mistake
Assuming every signed-in role must read would reproduce the defect.
WHAT THE DEMONSTRATOR DID
YOUR LEARNING CONTROLS
Make the skill your own.
Which action is the maintainer authorised to perform?
Watch the apparatus change as the student demonstrates. Take control whenever you want to test the same idea yourself.
BASED ON YOUR ATTEMPTS
Watching and practising are recorded separately in this visit. These examples do not change your assessed work or skills passport.
NOW TRANSFER THE SKILL
Carry the method into your own work.
The assigned role policy grants different read rights. Copying this completed matrix would apply the wrong authority.
A COMPLETE WORKED SUBMISSION
The embargoed observatory charter — completed record
Example work from this demonstration's scenario. Use it to understand the expected evidence and explanation, then make your own decisions in the assigned activity.
Download the complete exampleRead the finished work
Completed demonstration example — embargoed observatory permission audit
Authored alternate example. Read this local research embargo before deciding any permission.
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 |
The other seven decisions already matched. The first failure exposed an embargoed resource; the second blocked an authorised reader.
Version 1 — repaired charter
| Role | Read | Service | Approve | | --- | --- | --- | --- | | Reader | Allow | Deny | Deny | | Maintainer | Deny | Allow | Deny | | Custodian | Allow | Deny | Allow |
All nine cells were compared with the charter. Positive checks preserved reader reading, maintainer service and custodian reading/approval. Negative checks retained the embargo and remaining limits. The repair changed only maintainer/read and reader/read.
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.
Named output: permission-audit. These are fictional local decisions, not an external security test.
Method to carry forward
Derive expected permissions from a charter before testing observed behaviour.
The assigned role policy grants different read rights. Copying this completed matrix would apply the wrong authority.
The complete example explains one defensible approach. In your own challenge, select observations and tests from the supplied rules, keep your prediction separate from the result, and justify both the checks you perform and those you omit.
The chapter investigation and its explained record complete the core method. The scene delivery is an optional extension; it is not evidence of deeper understanding on its own.
Complete transcript and decisions · readable without JavaScript
Before we begin · expected task and evidence
I must repair the observatory’s embargo charter. Maintainers may service equipment but may not read research. I will preserve an excessive permission and a missing required permission, repair the two cells, retest the complete matrix and then apply a narrow release hold. My audit must distinguish a bug from a later authorised change. The method we are practising is: Derive expected permissions from a charter before testing observed behaviour.. Our field objective is: Restore the telescope console permissions while preserving its embargo approval rule. Repairing the reader and custodian faults must not erase the hold or maintainer responsibilities. The investigation and explained record complete this lesson. A scene delivery is an optional extension. You can pause, mute, replay, or take control at any point. The captions show the same explanation.
1. Derive rights from this charter
What I need to do: Step 1. Derive rights from this charter. I derive each right from the explicit embargo rather than assuming service responsibility grants research visibility.
Supplied context: The research embargo separates two responsibilities. Readers may read research; maintainers may service equipment but may not read research; custodians may read and approve release. Every other combination is denied. A job title does not imply extra access.
Watch my actions: For "Maintainer authority", I choose "Service only". I check the demonstrated result.
What I observed: The maintainer needs service access without research visibility. The local charter defines the expected result. Equipment responsibility and research visibility are separate permissions in this local model.
Why: Equipment responsibility and research visibility are separate permissions in this local model.
Decision: Which action is the maintainer authorised to perform?
- Maintainer authority: Service only
Result: The maintainer needs service access without research visibility. The local charter defines the expected result.
Common mistake: Assuming every signed-in role must read would reproduce the defect.
2. Record an excess right and a missing right
What I need to do: Step 2. Record an excess right and a missing right. I record both actual failures before editing: forbidden maintainer reading and blocked reader reading.
Supplied context: The observed policy allows maintainer reading even though the embargo forbids it. It also denies reader reading even though the charter requires it. The demonstrator records both failures before changing anything.
Watch my actions: For "Observed maintainer / read", I choose "Allow". For "Observed reader / read", I choose "Deny". I check the demonstrated result.
What I observed: The audit preserves a forbidden success and a required operation that failed. Both need repair. A policy can simultaneously expose information and prevent legitimate work.
Why: A policy can simultaneously expose information and prevent legitimate work.
Decision: Record the observed results, even though both contradict the charter.
- Observed maintainer / read: Allow
- Observed reader / read: Deny
Result: The audit preserves a forbidden success and a required operation that failed. Both need repair.
Common mistake: Recording only the excessive permission would miss the blocked reader.
3. Repair the two affected decisions
What I need to do: Step 3. Repair the two affected decisions. I correct only the two mismatched cells and preserve the seven already valid decisions.
Supplied context: The demonstrator denies maintainer reading and restores reader reading. Maintainer service remains allowed. Custodian reading and release approval remain allowed. The other four denied combinations are retained.
Watch my actions: For "Policy repair", I choose "Deny maintainer; allow reader". I check the demonstrated result.
What I observed: Exactly the two observed mismatches are corrected under the published charter. The repair must remove excess authority and restore required work without inventing a broader role.
Why: The repair must remove excess authority and restore required work without inventing a broader role.
Decision: Choose the smallest complete repair.
- Policy repair: Deny maintainer; allow reader
Result: Exactly the two observed mismatches are corrected under the published charter.
Common mistake: Denying all reading prevents the exposure but also violates reader and custodian duties.
4. Check that useful work remains possible
What I need to do: Step 4. Check that useful work remains possible. I retest positive and negative cases, including the different reading results for reader and maintainer.
Supplied context: The repaired policy passes all nine expected decisions. Positive checks include reader reading, maintainer service and custodian approval. Negative checks include maintainer reading and reader approval. The demonstrator records the complete table.
Watch my actions: I set "Reader may read research" to yes. I set "Maintainer may read research" to no. I check the demonstrated result.
What I observed: The reading results differ by role; the repaired table also preserves maintenance and release duties. Testing only forbidden requests cannot show whether a repair preserves useful work.
Why: Testing only forbidden requests cannot show whether a repair preserves useful work.
Decision: Set the two regression results that distinguish this charter.
- Reader may read research: Yes
- Maintainer may read research: No
Result: The reading results differ by role; the repaired table also preserves maintenance and release duties.
Common mistake: Giving every role research-reading permission would violate this embargo.
5. Apply a release hold without changing the embargo
What I need to do: Step 5. Apply a release hold without changing the embargo. I apply the new release hold only to custodian approval and keep the research embargo unchanged.
Supplied context: A new signed release hold suspends custodian approval. Reader and custodian reading remain permitted. Maintainer service remains permitted, while maintainer research reading is still forbidden. Version 1 is retained beside the changed authority.
Watch my actions: I set "Custodian approval during release hold" to no. I check the demonstrated result.
What I observed: Only custodian approval changes. The earlier matrix was correct under its original authority. An authorised change must be scoped to the operation it names.
Why: An authorised change must be scoped to the operation it names.
Decision: Apply the release hold.
- Custodian approval during release hold: No
Result: Only custodian approval changes. The earlier matrix was correct under its original authority.
Common mistake: Treating the hold as permission to reveal embargoed records changes an unrelated rule.
6. Explain repair separately from authorised change
What I need to do: Step 6. Explain repair separately from authorised change. I attach the governing charter or notice to each result so the two versions remain explainable.
Supplied context: The completed audit keeps the original two failures, the nine-cell repaired matrix, the positive and negative checks, and the later release hold. The demonstrator labels each with its governing charter or notice.
Watch my actions: For "Reason for the two versions", I choose "V1: bug fixes; V2: new hold". I check the demonstrated result.
What I observed: The audit explains each changed result without rewriting the historical charter. A reviewer must distinguish a bug from a changed requirement.
Why: A reviewer must distinguish a bug from a changed requirement.
Decision: Choose the explanation that preserves both events.
- Reason for the two versions: V1: bug fixes; V2: new hold
Result: The audit explains each changed result without rewriting the historical charter.
Common mistake: A clean final table alone conceals why earlier outcomes differed.
Optional field extension
All chapter evidence checks are complete. I return to the mission station and apply the tested charter. I am putting the verified solution into effect, then checking what changes.
I collect Observatory charter and regression record. The verified intervention released this package. I now carry it through the marked handover route.
I carry Observatory charter and regression record to Telescope console. I confirm this checkpoint before continuing so the handover trace records the route actually followed.
I carry Observatory charter and regression record to Custodian audit desk. I confirm this checkpoint before continuing so the handover trace records the route actually followed.
At the receiving station, I hand over the permission audit. I check the receipt before calling the field operation complete.
My observations and finished submission
The faulty table allowed maintainer research reading and blocked reader reading. I denied the former and restored the latter without removing service or custodian duties. All nine decisions then matched the embargo charter. A later release hold changed only custodian approval. My completed audit retains the failed tests and both justified versions; the assigned lab has a different reading rule and must be derived afresh. Derive expected permissions from a charter before testing observed behaviour. Open "Read the finished work" or download the complete example to inspect the evidence and explanation together. The assigned role policy grants different read rights. Copying this completed matrix would apply the wrong authority.
The complete submission is available in Read the finished work above and as a Markdown download.