Institution workspace, computed locally
- Choose files: the loan extract from your core banking export (required), the control totals, a saved mapping profile and your project file.
- Check data: read the findings; download the correction file when rows were rejected; confirm the mapping profile and save it for next month.
- Open the risk review: the queue ranks rows the frozen engines already produced; nothing new is computed about risk.
- Record actions in the register with maker and checker labels. These are workflow labels, not authenticated access control.
- Export the project file to keep snapshots, profiles and the register. Nothing is stored in the browser between visits.
Guided import
contract sections 2 to 5 · laghubitta-workflow.jsStep 1 · Choose files
Files are read in this tab, hashed with SHA-256 and parsed by the v1 parser. No file leaves the browser. Columns that look like names, phone numbers, addresses or citizenship numbers stop the import.
Step 3 · Open the risk review
Builds the v1 dataset, runs the Tier 1 v2 engine with the default configs and stores a validated snapshot in the project. Enabled only when the check found no error.
Check the data first.Advanced: balance sheet (NPR, whole rupees)
When these six fields are empty the balance sheet is recorded as not supplied (ruling WR7): the engines still run with a balance sheet sized from the portfolio, not supplied, but capital adequacy, liquidity coverage and every stress figure derived from them read unavailable, the review queue carries a data gap and no capital or liquidity breach is reported. Enter all six figures to evaluate them.
Step 2 · Check data
no file checkedErrors (block the snapshot)
Warnings (carried into the snapshot and every report)
Information
Reconciliation against control totals
| as_of | metric | control | computed | difference | status |
|---|
Counts match exactly; NPR within one millionth of the control. A variance never blocks the snapshot; it becomes an attention item.
Daily risk review
What needs attention
Rows the frozen engines produced, ordered by severity, materiality (branch gross share), deterioration against the comparison period, age, then identifiers. Duplicates of one branch and family form one card.
What changed
What action is pending
Missing data
ruling R6: a missing input is never a low riskAction register
contract section 8 · states open, in review, awaiting checker, closed, overriddenWorkflow labels, not authenticated access control: maker and checker are free text labels typed by the user; the workspace has no login and cannot verify who typed a label. The register never writes to the core banking system, never changes a loan and never produces a lending decision.
| Title | Owner | Due | Status | Stage | Maker | Checker | Resolution | Exposure |
|---|
Overdue items are highlighted. Select a row to edit it.
Selected item
noneSelect an item in the table.
Audit events
Reminders (dry run outbox)
contract section 11 · dry run only · no approved connector"Check reminders" raises escalation stages on overdue items, writes outbox entries (overdue, escalation, requested reminders) and runs the dry run. In app entries are delivered in this panel; email and sms entries read "Delivery unavailable: no approved connector". Nothing leaves the page.
Reports
contract section 9 · generated in your browser from the current validated snapshot · nothing is sent anywhereProvenance header (printed on every page)
DRAFTReview and downloads
A report is DRAFT when generated. It reads REVIEWED only when a report_reviewed note with a reviewer label is recorded for this snapshot and the reconciliation is not a variance (or every variance has a register item in closed or overridden state). Reviewer, maker and checker are workflow labels, not authenticated access control.
Reports
Two documents from one validated snapshot plus the register: the management brief (markdown, machine readable, user labels through text safety) and the committee packet (the brief followed by the board pack sections over the stored blocks). Print uses the browser (A4); page numbers follow the browser. The bundled sample board pack is never exported as an institution report.
Key indicators (on screen; the packet keeps crore)
Committee packet (preview; the same nodes print)
Ask
contract section 10 · five intents · answers only from the stored validated snapshot, the register and the frozen explanation stringsDeterministic templates over the calculation results, not machine learning. No free text generation, no model call, no network: the question is matched against a keyword table and answered by a fixed template whose figures carry evidence references into the stored snapshot.
No question asked yet. Choose a suggested question or type one.
Every number goes through the frozen formatters; every explanation string is copied verbatim from the engine output; evidence references open the stored row. An adapter, if one were ever configured, would run outside the browser on the institution's own machine and its text would be shown beside the template answer, never instead of it; the browser build holds only the mock adapter and no key of any kind.
My day
contract section 5 · my-day · due register work, today's sessions, recent drafts, due remindersIn memory, not saved to a serverIncluded in the project file when you export it
Labels typed here are workflow labels, not authenticated access control.
Due actions
Today's sessions and events
Recent drafts
Due reminders (in app, dry run)
Calendar
contract sections 2.1, 3.1, 3.5 · day, week, month, agenda · occurrence and series edits · in app reminders, dry run onlyIn memory, not saved to a serverIncluded in the project file when you export it
Occurrences
| Date | Time | Kind | Title | Branch scope | Recurring | Actions |
|---|
Reminders (planned, in app, dry run)
contract section 3.5 · idempotency key over event, occurrence date, offset and channel · a cancelled reminder never re enqueuesIn app only. Email, SMS and external calendar sync do not exist in this workspace.
| Fire at | Title | Status | Key | Actions |
|---|
Notes
contract sections 2.3, 3.3, 3.4, 6 · private by default · revisions · stale saves refused with both drafts · text onlyIn memory, not saved to a serverIncluded in the project file when you export it
Notes
| Title | Kind | Visibility | State | Revision | Updated | Attached to |
|---|
Selected note
noneSelect a note or create one.
Conflict: a save from a stale revision was refused. Both drafts are kept; choose how to resolve.
Current revision (theirs)
Your refused draft (mine)
Share with
Revisions
| Revision | Saved at | By | Base | Origin | Body sha256 | Actions |
|---|
Sessions
contract sections 2.2, 3.2 · planned, in progress, minutes draft, minutes reviewed · reviewer distinct from the authorIn memory, not saved to a serverIncluded in the project file when you export it
Sessions
| Title | When | Status | Participants |
|---|
Selected session
noneSelect a session or create one.
Reviewed: the session and its minutes are frozen. Minutes are never a report release.
Committee decisions
Notes taken in this session
Project
cbsrm-project/1.0.0 · explicit export and import only · nothing in browser storageA project file holds snapshots (provenance, import check, reconciliation, results) and the register, never the loans extract. Customer and sample data never share a project file.
Validated snapshots
Failed imports (kept apart, never the latest validated)
Quarantined snapshots (ruling WR9: balance sheet evidence missing or inconsistent; no review until the data request is answered)
Mapping profiles in the project
Project audit events
Help
language: en (source); ne keys present, untranslatedThe full help page (three languages) opens in a new tab: what each step does, what the institution file must contain, units, draft and reviewed, data separation, and what this is not.