JKSSB Vault — working rules

This is an Obsidian vault for JKSSB exam preparation, targeting the Finance Account Assistant (FAA) exam on 15 November 2026.

🔴 RULE 1 — Read PROJECT-LOG.md first

Before doing anything in this vault, read PROJECT-LOG.md at the vault root. It is the single source of truth: what exists, why it was built, every finding and correction, and what is still open. It will save you from repeating work already done and from mistakes already made and documented.

Then read Home.md for navigation.

🔴 RULE 2 — Update PROJECT-LOG.md whenever you change anything

Every session that creates, changes, corrects or discovers something MUST update PROJECT-LOG.md before ending — in the same session.

You did this	Update
Created/changed a file	§5 file map
Found an error or dated content	§3 findings
Filled a gap / added an addendum	§4
Finished an open item	§7 — tick it off
Found a new open item	§7 — add it
Reached a new conclusion	§6
Did substantial new work	§2 chronology

Also bump last-updated in its frontmatter and add a row to §10 Change history. For long tasks, update as you go — not only at the end.

Never delete history from that file. If something turns out to be wrong, add a dated correction that supersedes it, so the mistake stays visible and is not repeated.

🔴 RULE 3 — Never alter source exam material

Question papers, answer keys and the author's chapter notes are source data. Edits to them must be additive only — YAML frontmatter, a clearly marked ADDENDUM section, or [!pyq] / [!fix] callouts. Never rewrite, "fix" or delete original questions, options, answers or the author's text. If something in the source is wrong, flag it beside the content; do not silently change it.

Conventions in this vault

Paper codes: WO · WG · IN · JA · GD · LA · SF (the 7 completed 2026 papers)
Question-bank row format: Source | Question | Options | Ans | Explanation, options in their own column with bolded **A)** letters
Aliased wikilinks inside tables must escape the pipe: [[NoteWO]]
Custom callouts: [!pyq] = gold "this came in the exam" · [!fix] = red "outdated/incorrect" (defined in .obsidian/snippets/exam-callouts.css — must be enabled in Settings → Appearance)
Short notes follow a fixed 6-block shape: exam weight → core → quick revision table → 🎯 PYQs → MCQ traps → "if you remember nothing else"
Dataview output does NOT create Graph View edges — only real [[wikilinks]] and tags do
Verify every wikilink resolves before finishing; broken links are treated as bugs here

Working style the user expects

Work in sequence (e.g. chapter order) unless told otherwise
Prefer tables over prose
Show a sample and get approval before doing bulk work
Flag errors, gaps and dated content honestly — do not paper over them
Produce one consolidated file at the end of a multi-part series