Sable · Projects

How Projects work

A short briefing for IT and everyone who will use a project page. Send this link. Do not email a file — a large HTML attachment is quarantined and reaches nobody.

1. What a Project is

A Project is a folder with a permanent code such as PRJ-0003. Inside it are named outputs (Cash flow, BRD, and so on) — not department-report ids such as F14 or R1. Those remain a different product with a different people list.

Department on a Project is a label (Finance, Stores, IT). It does not issue a report number.

2. Two ways to start — one URL

1. In Sable. Signed-in person opens Projects, picks a department label, names the project and the first output. Sable returns the admin URL immediately.
2. From a session. The person gives the session their current master code (on Me) and their email — primary or any address linked on Me. The session creates the same Project and gets the same admin URL back.

That URL is personal. Opening it in a browser sets a cookie and cleans the address bar — the short path left behind is not a shareable link. Copy for session is the same URL pasted into an AI session. An invited person needs their Copy page link (browser) and Copy for session (AI session), not yours and not the address bar.

3. Publishing the BRD — session, upload, or Iris

Once you hold a write or admin URL, any of these writes the page. None of them revoke anyone or mint new links. People join by invite on the Project in Sable, each with their own link.

1. AI session. Paste Copy for session, then:
   node scripts/publish-project-brd.cjs --url "<pasted URL>" --html ./brd.html --yes
2. In the browser. On the Project in Sable, Upload HTML to get started — a file that carries the boot marker. The page token in your link is the authority. No fleet secret.
3. Ask Iris to build this page. She drafts from the locked design (docs/PROJECT_DOC_DESIGN_LOCK.md and samples/project-brd/PRJ-0001_reference.html). Paste Copy for session when she asks for the URL so she can publish. Do not email the document.

A read-only invitee can read in the browser. Admin and collaborator may comment, publish, and upload. Only admin invites, rewinds, and marks complete.

4. Comments and files

Everyone with write or admin on that output comments on the live page. They may attach a file to a comment (Word, Excel, PDF, images, and the other allow-listed types, up to the page engine's size cap). Files live on the Project. A session that refreshes reads those comments and file names the same way it reads the text.

5. Refresh

Comments save as they are typed. When someone asks to refresh, a session holding the pasted URL reads context, summary, comments, and file paths, then publishes a new edition. History only grows. Rewind publishes an older page as a new edition; comments stay.

6. Departments and report letters

Access departments (who may see company data on any channel) and report letters are related but not the same thing. The table is the list; it is not a count.

IT is a department. Superadmin (Samarth) may add another department and give it a report letter. Letters are permanent: they are never renamed, deleted, or reused. Marketing is an access label and does not yet have a letter.

Admin assigns which departments a person may receive data for. Admins hold every department automatically.

7. Who does what

Questions: use Sable Projects, or ask IT. This briefing is the living page at the URL above — if the product changes, this page changes with it.