Cross-Entity Disclosure Tracker
Overview
Use this skill as a Busabase-backed review-workspace desk for a compliance/IR
team assembling a standardized disclosure package per financing vehicle (fund
or SPV). Each vehicle's package spans three generic entity roles:
- Origination entity — the onshore entity that originates/services the
underlying assets.
- Fund-manager entity — the offshore entity that manages the vehicle.
- Listing venue — the exchange/listing venue where the vehicle's notes or
units are listed.
This is a generic, brand-free tool: no real company, regulator, or exchange
is referenced anywhere in the skill, its data, or its UI. All vehicle and entity
names in seed data are synthetic placeholders ("SPV Alpha 12", "Onshore
Originator A", "Exchange One", and so on).
Default behavior is AirApp-first. Unless the user explicitly asks only for
explanation, ensure the mock portfolio exists (run the seed script below if the
vehicles Base is empty) and give the user the clickable AirApp URL (or the
local preview URL when local preview is explicitly requested). Use chat-only
mode only when the user says "纯聊天", "chat only", "不要打开 UI", or similar.
This is a workspace/review-queue hybrid: the human works through a
checklist per vehicle rather than approving a linear queue, but the underlying
mechanics (statuses, decisions, writing straight to Busabase) follow the same
App-in-Skill review model used elsewhere in this batch.
App UI Screenshots
Mandatory Dependencies
- Read and follow
$kelly-app-skill-creator for product behavior, visual quality, responsive layout, and the complete canonical content/kelly-disclosure-tracker-app/ artifact.
- Read and follow
$busabase for connection, target Space, node discovery, ChangeRequests, review, and merge behavior.
- Read and follow
$busabase-app-creator for resource modeling, AirApp runtime limits, security, validation, and deployment.
If a dependency is unavailable, preserve this skill's local artifact and product contracts, stop before the unavailable Busabase operation, and report the exact missing dependency. Do not invent a second data backend.
Boundary
- Review workspace only. The skill reads and writes its own Busabase Bases;
it never calls any external system, filing portal, or exchange API.
- NEVER file, submit, or transmit anything to a real regulator, fund
administrator, or exchange. There is no filing path in this skill by design.
- The AirApp reads and writes its own three Busabase Bases only.
- Treat all vehicle/entity data as sensitive by convention, even though the
bundled seed data is synthetic.
Busabase Resources
Three Bases under one application Folder (kelly-disclosure-tracker),
declared in content/kelly-disclosure-tracker-app/app/js/config.js and the generated template sidecars under content/:
vehicles: one row per financing vehicle (fund/SPV) — the origination
entity, fund-manager entity, listing venue, base currency, and target close
date. Per-vehicle checklist completeness/readiness is never stored — it is
recomputed client-side from the items Base on every read.
items: one row per standardized disclosure checklist item, scoped to a
vehicle and one of the three entity roles. Carries the raw checklist
fields, an optional cross-entity reconciliation record, the reviewer's
decision (decision-action/decision-comment/decided-at/
override-reconciliation), and — once scripts/execute_decisions.mjs
runs — an execution marker, all written directly onto the same row. Status
is never stored — it is recomputed client-side from decision +
reconciliation on every read.
settings: up to two rows, keyed by record-id/kind: config
(reviewer name) and run (the current batch's batch id + generated-at).
Resources provision lazily through an idempotent Busabase ChangeRequest the
first time the app runs in a Space; see references/ui-schema.md for exact
field shapes.
First Run And Onboarding
On invocation, check the vehicles Base. If it's empty, run the trusted seed
script to generate the fixed mock portfolio:
node skills/kelly-disclosure-tracker/scripts/generate_batch.mjs --apply
There are no credentials to collect beyond Busabase itself — onboarding is
just confirming the reviewer's display name in the settings Base's config
row (defaults to "Unassigned reviewer" if omitted).
Local App
Default behavior is AirApp-first — give the user the clickable AirApp URL.
Start pnpm --dir content/kelly-disclosure-tracker-app dev only when local preview/debugging is explicitly
requested.
Required app views (hash routes):
#/overview (default route): portfolio-level hero and a 3-number metrics
band (vehicles tracked, in progress, items flagged), plus a readiness
breakdown and a "needs attention" queue across every vehicle.
#/vehicles: one row per financing vehicle in a full-bleed table;
?filter=needs_review|changes_requested|blocked|ready narrows it.
#/vehicles/<vehicle_id>: the vehicle opens as a full page (its own
workplace, not a drawer/peek) with the checklist grouped by role and
per-vehicle metrics.
#/vehicles/<vehicle_id>/<item_id>: item detail + decision panel (verified /
needs source / flag inconsistent) with a reviewer note, shown inside the
vehicle page. Decisions write directly onto the item record through
busabase-sdk.
#/flagged: a full-bleed table of every item currently flagged, across all
vehicles; a row has no detail panel of its own — it opens straight into the
owning vehicle's item (#/vehicles/<vehicle_id>/<item_id>).
#/settings: sanitized setup summary — data provider, reviewer name,
onboarding state.
Demo Mode
?demo=1 opens a deterministic, fully offline mock portfolio (9 vehicles,
6 items each) for documentation and screenshots. Demo mode never reads or
writes Busabase.
lang=en or lang=zh forces UI chrome language for screenshots.
UI language: support English and Chinese (zh-CN) chrome with Auto default.
Workflow
node scripts/generate_batch.mjs --apply (dry run without --apply)
writes the fixed 9-vehicle / 54-item mock portfolio to the vehicles and
items Bases (resetting every item's decision fields to the standard
pre-seeded mix) and refreshes the settings Base's run row — run it
once at setup, and again any time the demo portfolio needs resetting.
- Open the app. Vehicles shows the portfolio summary and the vehicle
grid; Flagged lists every cross-entity reconciliation mismatch or
reviewer-flagged inconsistency in one place.
- For each vehicle, open its checklist grouped by role (origination /
fund-manager / listing venue), select an item, and record
Verified /
Needs source / Flag inconsistent with an optional reviewer note —
written straight onto the item record. A "Verified" decision on an item
with an unresolved reconciliation mismatch is held at "Awaiting source"
until the reviewer explicitly acknowledges the mismatch.
node scripts/execute_decisions.mjs --apply (dry run without --apply)
re-reads Busabase and writes an execution marker (execution-status,
execution-detail, executed-at) onto every item, reporting which are
settled (verified/done or flagged/blocked) vs still awaiting a human
decision. It performs no external side effect — no filing, no submission,
no transmission to a regulator, fund administrator, or exchange.
Read references/ui-schema.md before editing the app, scripts, or
content/kelly-disclosure-tracker-app/app/js/tracker-model.js.
The Domain Model (not a filing system)
content/kelly-disclosure-tracker-app/app/js/tracker-model.js documents and implements the entire domain
model: the fixed seed portfolio (buildSeedData()), the per-item decision ->
status mapping (computeItemStatus(), including the reconciliation-mismatch
guardrail), and the per-vehicle/portfolio rollups
(computeVehicleMetrics()/computeReadiness()/computeBatchMetrics()).
Every function is pure and deterministic — same inputs always produce the
same output — so a human reviewer can audit every status and count by hand.
It backs the trusted seed script (scripts/generate_batch.mjs), the live
Busabase read path (content/kelly-disclosure-tracker-app/app/js/providers/busabase-provider.js), and the
offline ?demo= scenario (content/kelly-disclosure-tracker-app/app/js/providers/demo-provider.js), so all
three always agree on the portfolio and its statuses.
Safety
- Review workspace only: never file, submit, or transmit anything to a real
regulator, fund administrator, or exchange — there is no filing path in
this skill by design.
- Do not invent reconciliation figures beyond the deterministic demo/seed
data; real usage should have the skill populate the
vehicles/items
Bases from actual source documents before asking the human to review.
- Redact anything that looks like a real credential or account number in
logs, reports, and UI state (none are expected in this skill's data
model).
- Keep the seed portfolio minimal and use stable item ids so repeated seeds
stay idempotent (the seed script upserts by
vehicle-id/item-id, never
duplicating rows).
Useful Commands
node skills/kelly-disclosure-tracker/scripts/generate_batch.mjs --apply
node skills/kelly-disclosure-tracker/scripts/execute_decisions.mjs --apply
pnpm --dir skills/kelly-disclosure-tracker/content/kelly-disclosure-tracker-app dev
1---2name: kelly-disclosure-tracker3description: Cross-Entity Disclosure Tracker App-in-Skill — a Busabase review workspace that helps a compliance/IR team assemble and track a standardized disclosure package per financing vehicle (fund/SPV), across a generic onshore origination entity, an offshore fund-manager entity, and a listing/exchange venue. Use when the user invokes $kelly-disclosure-tracker or /kelly-disclosure-tracker, wants to review disclosure checklists, vehicle readiness, cross-entity reconciliation flags, or reviewer notes across multiple financing vehicles. Review workspace only — it never files anything or calls any external system.4metadata:5 source: https://skillmd.com/skills/mr-kelly/kelly-disclosure-tracker6 category: rbf7 tags:8 - risk:sandbox9 - surface:busabase10 busabase:11 template: true12 folderSlug: kelly-disclosure-tracker13 resources:14 - vehicles15 - items16 - settings17 risk: sandbox1819---2021# Cross-Entity Disclosure Tracker2223## Overview2425Use this skill as a Busabase-backed review-workspace desk for a compliance/IR26team assembling a standardized disclosure package per financing vehicle (fund27or SPV). Each vehicle's package spans three generic entity roles:2829- **Origination entity** — the onshore entity that originates/services the30 underlying assets.31- **Fund-manager entity** — the offshore entity that manages the vehicle.32- **Listing venue** — the exchange/listing venue where the vehicle's notes or33 units are listed.3435This is a **generic, brand-free** tool: no real company, regulator, or exchange36is referenced anywhere in the skill, its data, or its UI. All vehicle and entity37names in seed data are synthetic placeholders ("SPV Alpha 12", "Onshore38Originator A", "Exchange One", and so on).3940Default behavior is AirApp-first. Unless the user explicitly asks only for41explanation, ensure the mock portfolio exists (run the seed script below if the42`vehicles` Base is empty) and give the user the clickable AirApp URL (or the43local preview URL when local preview is explicitly requested). Use chat-only44mode only when the user says "纯聊天", "chat only", "不要打开 UI", or similar.4546This is a **workspace/review-queue hybrid**: the human works through a47checklist per vehicle rather than approving a linear queue, but the underlying48mechanics (statuses, decisions, writing straight to Busabase) follow the same49App-in-Skill review model used elsewhere in this batch.5051## App UI Screenshots5253<table>54 <tr>55 <td width="50%"><img src="assets/screenshots/overview.webp" alt="Disclosure Tracker overview"></td>56 <td width="50%"><img src="assets/screenshots/vehicle-detail.webp" alt="Disclosure Tracker vehicle detail"></td>57 </tr>58 <tr>59 <td><strong>Overview</strong><br>Portfolio-level summary (ready / blocked / in-progress vehicles) plus the vehicle grid.</td>60 <td><strong>Vehicle detail</strong><br>Checklist grouped by role (origination / fund-manager / listing venue) with a decision panel: verified, needs source, or flag inconsistent, plus a reviewer note.</td>61 </tr>62 <tr>63 <td colspan="2"><img src="assets/screenshots/flagged.webp" alt="Disclosure Tracker flagged items"></td>64 </tr>65 <tr>66 <td colspan="2"><strong>Flagged</strong><br>Cross-entity reconciliation mismatches (e.g. a figure that doesn't reconcile between the fund-manager's AUM statement and the listing venue's filing) and reviewer-flagged inconsistencies, in one list.</td>67 </tr>68</table>6970## Mandatory Dependencies71721. Read and follow `$kelly-app-skill-creator` for product behavior, visual quality, responsive layout, and the complete canonical `content/kelly-disclosure-tracker-app/` artifact.732. Read and follow `$busabase` for connection, target Space, node discovery, ChangeRequests, review, and merge behavior.743. Read and follow `$busabase-app-creator` for resource modeling, AirApp runtime limits, security, validation, and deployment.7576If a dependency is unavailable, preserve this skill's local artifact and product contracts, stop before the unavailable Busabase operation, and report the exact missing dependency. Do not invent a second data backend.7778## Boundary7980- Review workspace only. The skill reads and writes its own Busabase Bases;81 it never calls any external system, filing portal, or exchange API.82- NEVER file, submit, or transmit anything to a real regulator, fund83 administrator, or exchange. There is no filing path in this skill by design.84- The AirApp reads and writes its own three Busabase Bases only.85- Treat all vehicle/entity data as sensitive by convention, even though the86 bundled seed data is synthetic.8788## Busabase Resources8990Three Bases under one application Folder (`kelly-disclosure-tracker`),91declared in `content/kelly-disclosure-tracker-app/app/js/config.js` and the generated template sidecars under `content/`:9293- `vehicles`: one row per financing vehicle (fund/SPV) — the origination94 entity, fund-manager entity, listing venue, base currency, and target close95 date. Per-vehicle checklist completeness/readiness is never stored — it is96 recomputed client-side from the `items` Base on every read.97- `items`: one row per standardized disclosure checklist item, scoped to a98 vehicle and one of the three entity roles. Carries the raw checklist99 fields, an optional cross-entity reconciliation record, the reviewer's100 decision (`decision-action`/`decision-comment`/`decided-at`/101 `override-reconciliation`), and — once `scripts/execute_decisions.mjs`102 runs — an execution marker, all written directly onto the same row. Status103 is never stored — it is recomputed client-side from decision +104 reconciliation on every read.105- `settings`: up to two rows, keyed by `record-id`/`kind`: `config`106 (reviewer name) and `run` (the current batch's batch id + generated-at).107108Resources provision lazily through an idempotent Busabase ChangeRequest the109first time the app runs in a Space; see `references/ui-schema.md` for exact110field shapes.111112## First Run And Onboarding113114On invocation, check the `vehicles` Base. If it's empty, run the trusted seed115script to generate the fixed mock portfolio:116117```bash118node skills/kelly-disclosure-tracker/scripts/generate_batch.mjs --apply119```120121There are no credentials to collect beyond Busabase itself — onboarding is122just confirming the reviewer's display name in the `settings` Base's `config`123row (defaults to "Unassigned reviewer" if omitted).124125## Local App126127Default behavior is AirApp-first — give the user the clickable AirApp URL.128Start `pnpm --dir content/kelly-disclosure-tracker-app dev` only when local preview/debugging is explicitly129requested.130131Required app views (hash routes):132133- `#/overview` (default route): portfolio-level hero and a 3-number metrics134 band (vehicles tracked, in progress, items flagged), plus a readiness135 breakdown and a "needs attention" queue across every vehicle.136- `#/vehicles`: one row per financing vehicle in a full-bleed table;137 `?filter=needs_review|changes_requested|blocked|ready` narrows it.138- `#/vehicles/<vehicle_id>`: the vehicle opens as a full page (its own139 workplace, not a drawer/peek) with the checklist grouped by role and140 per-vehicle metrics.141- `#/vehicles/<vehicle_id>/<item_id>`: item detail + decision panel (verified /142 needs source / flag inconsistent) with a reviewer note, shown inside the143 vehicle page. Decisions write directly onto the item record through144 `busabase-sdk`.145- `#/flagged`: a full-bleed table of every item currently flagged, across all146 vehicles; a row has no detail panel of its own — it opens straight into the147 owning vehicle's item (`#/vehicles/<vehicle_id>/<item_id>`).148- `#/settings`: sanitized setup summary — data provider, reviewer name,149 onboarding state.150151## Demo Mode152153- `?demo=1` opens a deterministic, fully offline mock portfolio (9 vehicles,154 6 items each) for documentation and screenshots. Demo mode never reads or155 writes Busabase.156- `lang=en` or `lang=zh` forces UI chrome language for screenshots.157158UI language: support English and Chinese (zh-CN) chrome with `Auto` default.159160## Workflow1611621. `node scripts/generate_batch.mjs --apply` (dry run without `--apply`)163 writes the fixed 9-vehicle / 54-item mock portfolio to the `vehicles` and164 `items` Bases (resetting every item's decision fields to the standard165 pre-seeded mix) and refreshes the `settings` Base's `run` row — run it166 once at setup, and again any time the demo portfolio needs resetting.1672. Open the app. **Vehicles** shows the portfolio summary and the vehicle168 grid; **Flagged** lists every cross-entity reconciliation mismatch or169 reviewer-flagged inconsistency in one place.1703. For each vehicle, open its checklist grouped by role (origination /171 fund-manager / listing venue), select an item, and record `Verified` /172 `Needs source` / `Flag inconsistent` with an optional reviewer note —173 written straight onto the item record. A "Verified" decision on an item174 with an unresolved reconciliation mismatch is held at "Awaiting source"175 until the reviewer explicitly acknowledges the mismatch.1764. `node scripts/execute_decisions.mjs --apply` (dry run without `--apply`)177 re-reads Busabase and writes an execution marker (`execution-status`,178 `execution-detail`, `executed-at`) onto every item, reporting which are179 settled (verified/done or flagged/blocked) vs still awaiting a human180 decision. It performs no external side effect — no filing, no submission,181 no transmission to a regulator, fund administrator, or exchange.182183Read `references/ui-schema.md` before editing the app, scripts, or184`content/kelly-disclosure-tracker-app/app/js/tracker-model.js`.185186## The Domain Model (not a filing system)187188`content/kelly-disclosure-tracker-app/app/js/tracker-model.js` documents and implements the entire domain189model: the fixed seed portfolio (`buildSeedData()`), the per-item decision ->190status mapping (`computeItemStatus()`, including the reconciliation-mismatch191guardrail), and the per-vehicle/portfolio rollups192(`computeVehicleMetrics()`/`computeReadiness()`/`computeBatchMetrics()`).193Every function is pure and deterministic — same inputs always produce the194same output — so a human reviewer can audit every status and count by hand.195It backs the trusted seed script (`scripts/generate_batch.mjs`), the live196Busabase read path (`content/kelly-disclosure-tracker-app/app/js/providers/busabase-provider.js`), and the197offline `?demo=` scenario (`content/kelly-disclosure-tracker-app/app/js/providers/demo-provider.js`), so all198three always agree on the portfolio and its statuses.199200## Safety201202- Review workspace only: never file, submit, or transmit anything to a real203 regulator, fund administrator, or exchange — there is no filing path in204 this skill by design.205- Do not invent reconciliation figures beyond the deterministic demo/seed206 data; real usage should have the skill populate the `vehicles`/`items`207 Bases from actual source documents before asking the human to review.208- Redact anything that looks like a real credential or account number in209 logs, reports, and UI state (none are expected in this skill's data210 model).211- Keep the seed portfolio minimal and use stable item ids so repeated seeds212 stay idempotent (the seed script upserts by `vehicle-id`/`item-id`, never213 duplicating rows).214215## Useful Commands216217```bash218node skills/kelly-disclosure-tracker/scripts/generate_batch.mjs --apply219node skills/kelly-disclosure-tracker/scripts/execute_decisions.mjs --apply220pnpm --dir skills/kelly-disclosure-tracker/content/kelly-disclosure-tracker-app dev221```