The record

Built for the day somebody challenges it.

Most testing software is built to run an exam. This is built to reconstruct one, years later, in front of people whose job is to find the flaw.

Try it

Change one number. Watch the record catch it.

Every consequential action is chained to the one before it, and each department’s chain is checked every day. Try it on a sample record:

  1. Change the composite score.
  2. Verify the record.
  3. Then try to cover it up.
BugleAudit record · Captain 2027Records
VERSION_PUBLISHEDWritten form v3 frozen · 60 questions122a…4708
EXAM_SUBMITTEDC-7KQ4TZ9M · 60 of 60 answered2687…7362
SCORE_FINALIZEDC-7KQ4TZ9M · composite cda7…0dce
LIST_CERTIFIED14 ranked · 1 excluded, reason recorded2442…8114
RECORD_EXPORTEDPromotional process record · hashes verifiedfdbd…756a
DAILY_CHECKHead of the chain, recorded Mar 21 · 04:00fdbd…756a

Nothing has been changed. Verify the record, then try changing the score.

What the record holds

Four things you will be asked for.

Nothing edited after publication

What a candidate saw is frozen at the database level, and every consequential action is chained to the one before it. Editing a question afterwards cannot change what anyone was scored on.

Nobody vanishes from the list

Every candidate who sat is either ranked or explicitly excluded with a stated reason. There is no silent drop.

Item analysis for each written form

Difficulty, discrimination, how each distractor drew, the form’s reliability, and differential item functioning where groups are large enough — flags for someone qualified to interpret, with the sample size shown.

Exports that stand alone

The whole examination, from your request to the certified list with every approval by name, exports as one record, its hashes verified as it is made. So do the list, each appeal packet and the audit chain.

That is the product. This is where it came from.

Why a promotional examination should start from the record, and what we will and will not do.

The record · Bugle