Content governance, one accountable decision at a time.
Pigeonhole is the internal workspace for building, reviewing, and governing the UAE GP assessment pack.
Your decision queue
Agents research and draft. You set the boundary, decide exceptions, and keep the accountability trail intact.
Where this pack is in the handoff
Each stage owns a distinct job. Work pauses when a human decision or an unresolved concern is required.
What is happening now
Only active work, blockers, and decisions are shown here. The full record stays attached to the relevant run.
Tell the agents what this pack is for
These are the few decisions that belong to the Content Lead. Once recorded, the Brief becomes the visible boundary that people approve and agents must honour.
Create the governed draft pack
Give the work a durable internal name. Pigeonhole generates the technical identifier.
Brief recorded
Set the pack boundary
Be specific about the outcome and boundaries. Do not list domains, sources, topics, or questions—the agent workflow owns those proposals.
How the agent workflow is controlled
Every agent has a narrow job, a written rubric, a confidence rule, and a defined route when it cannot safely continue.
Before Agent 1 can work
The Pack Brief needs its owner confirmation, independent UAE GP review, and psychometric review. No model call is made while the gate is incomplete.
Creation pipeline
Agents 1–5 prepare a question for independent human medical and psychometric review.
After questions are used
These are a separate learning loop, not a shortcut to clinical or psychometric decisions.
People and access
Named people—not agents—approve the pack boundary, medical accuracy, psychometric quality, and access. Start with the next responsibility; the current access record stays visible while you act.
People currently assigned
Each entry shows the role, current access state, credential requirement, and end date for this pack.
Preparing the next people step
Pigeonhole is checking which accountable role needs attention next.
Give someone accessNamed login, role, and end date
Give each person their own login. Send the temporary password privately; Pigeonhole cannot reveal it later.
Record UAE GP reviewer verificationRequired before independent medical sign-off
Record the independent credential check after the reviewer has been assigned. This does not replace their separate approval of the Pack Brief.
Build the clinical map.
Establish the UAE GP topic structure before authoring. The map makes later diagnostic, coverage, and evidence decisions traceable.
Next required action
Diagnostic intent can be attached only to a specific clinical leaf—never to an unscoped topic.
How this pack moves forward
Complete each stage in order. The next stage becomes meaningful only when its prerequisite is recorded.
Create the first governed draft pack
Name the assessment workspace. Pigeonhole creates the technical setup identifier in the background.
Build the clinical map
Start with a domain, add its topics, then add precise subtopics. Only a subtopic can carry diagnostic intent.
Clinical map
The hierarchy you are building for the UAE GP pack.
Build this clinical branch
Choose the parent context first. Pigeonhole then offers only the valid next record: a domain, a topic within that domain, or a subtopic within that topic.
View technical record
Associate a misconception
Once a subtopic is precise enough, describe the misunderstanding it should test.
Create a diagnostic leaf in the blueprint to unlock this stage. This prevents unscoped item-family design.
Define what this pack must cover
Set the four lenses that every later question must fit: clinical domain, population, task, and care context.
What every question must answer
Each lens needs at least one active label before the pack can claim complete coverage.
Define one lens
Record the sources this pack can rely on
Register pack-level sources and their permitted use first. Later, each question still needs its own supporting claim and clinical review.
Add a source your team can stand behind
Confirm how this source may be used
Record the terms as they are. A restricted or pending source stays visible, but cannot be used as cleared item evidence.
Evidence handoff ledger
This shows the real state of the work. It does not bypass content-author or independent UAE GP reviewer responsibilities.
Team and access
Create and manage accountable access for this pack. Send temporary passwords privately; Pigeonhole stores only a password hash and cannot show it again.
Create staff access
Use the person’s email as both Staff ID and Login email. Choose their role carefully—roles determine what each person can approve.
Record independent credential verification
This unlocks clinical review only after a different accountable lead has checked the reviewer’s qualification and current validity.
Team directory
This is the current record for the selected pack. Change an end date or remove pack access here; every change is audited.
Open Team access to load the current directory.
Pigeonhole 1729 · assessment operations
Every insight in its place.
Pigeonhole
Every question has a purpose, every insight has a place.
Different perspectives should converge on one reliable assessment. All status labels are accountable human records: this workspace cannot invent a cleared source, verified qualification, or medical approval.
Pack and team setup
Sources, claims and ranges
Review queue
Claim a queued item before reviewing it. Medical review always precedes psychometric review.
Select an item
Keep each decision traceable
Drafts remain editable. Submitting locks the current revision and sends it to medical review first.
Draft