📌 Context Management System

The updateable context every project carries — its fixed facts, definitions, contacts, plans, operating instructions, permit shape, and AI behavior. The system reads this on every draft, audit, and AI response. Update here once; drift gets flagged everywhere automatically.

Working on project: No project selected · showing global counts
GUID
guidance rules
CON
contacts
PLAN
plans
OPS
procedures
PROMPT
AI prompts
NUMA
numbers pinned
WSP
word meanings

🧩 What the project IS

structure · sections · permit shape · version chain

📜Permit template

PTPL-

Reusable scaffolds for agency forms. Once defined, instantiating a new permit auto-scaffolds the required slots.

▸ Existing templates

🏷️Section names

PSEC-

For multi-part deliverables. Section name survives across DOC- versions — bind the live DOC- to the named section.

▸ Existing sections

🔗Version chain

VLNK-

When a new DOC- supersedes an older one — link them explicitly so the chain isn't guessed from titles.

▸ Walk chain from a DOC-

👥 Who's involved

contacts · PE-stamp loop · roles · licenses

☎️Contacts

CON-

Marinis (PE engineer · 631-…), HDR Semenick (rail engineering), Knauf Shaw (environmental counsel). Per-project so each project has its own working address book.

▸ Existing contacts
▸ 📥 Import contacts in bulk (CSV or vCard)
Paste a contact list. CSV example (header row optional): name, role, phone, email, license, notes. vCard: paste any .vcf export (macOS Contacts → File → Export, or iPhone Share). Auto-detects format. Each row creates a CON- in the selected project.

✍️PE-stamp loop

STMP-

Tracks who has what document out for signature. The "in-flight" list shows every DOC- currently with a PE.

▸ Documents out for stamp right now

📚 What we know (the facts)

official numbers · word meanings · studies · doc classifier

🔢Pin a number (audit drafts for drift)

NUMA-

The most useful one. Pin once, then scan any draft for drift.

▸ Audit text for drift
▸ Pinned numbers for this project

🎓Fields of study

FIELDS

What fields does this project's writing draw from? Used to ground generation + flag borrowed terminology.

▸ Current fields

📖Pin word meanings

WSP-

Project-specific terms whose meaning matters. "Grandfather" in CRISI ≠ legal grandfathering. "Mine" in NYSDEC ≠ regulated mine.

▸ Pinned word meanings

📄Studies & reports

STU-

Imported third-party deliverables with author, license, date of record.

▸ Existing studies

📋Doc-type classifier

DTCL-

Run any new file through the classifier to bucket it (correspondence · exhibit · study · permit form · support letter). Bucket drives intake.

🛠️ How we work + AI behavior

guidance rules · operating procedures · plans · system prompts

📌Guidance instructions

GUID-

Project rules. AI consults these before drafting / reviewing. Drift triggers a flag.

▸ Active rules for this project

📋Operating procedures

OPS-

Workflows, procedures, checklists, protocols. The "how" of working on this project.

▸ Procedures for this project

💼Plans (business · ops · strategic)

PLAN-

Track the active plan documents — Townline business plan v3, NYSDEC renewal operations plan, etc. Bonded to DOC- versions when filed.

▸ Plans for this project

🤖System prompts (AI behavior)

PROMPT-

What the AI should keep in mind when working on this project. Treated as instructions on every drafting/review/audit pass.

▸ Active prompts

📦 Context Templates

project-specific starter bundles · glossary + entities + workflows · "packs" internally

Active template

ACTIVE

What's seeding this workspace right now. Switch by activating any installed template below.

Loading…

📦Installed templates

INST

Click Make active to drive this workspace from a different template's glossary + workflows.

📚Template library

LIB

Pre-built starter templates for industries. Install one to add its vocabulary + workflows to this workspace.

💾Save workspace as template

SAVE

Turn this workspace's vocabulary + entities + workflows into a reusable template. Other workspaces can install it.

🆕 Start a new project

Pick a template, name the project, and the CMS will scaffold an initial set of guidance rules and procedures. You can add more from the cards below afterward.

▸ Optional: add one initial guidance rule
▸ Optional: add one initial official number
🔍 Cross-system audit
Loading…
✏️ Rename project

The PJE- barcode is permanent (it's the project's identity). Only the display name changes.

🗑 Delete project
This will permanently delete every CMS row for the project: guidance · contacts · plans · procedures · prompts · numbers · word meanings · sections · studies + the project's metadata row.

System-wide records that mention this project (permit templates, stamp loop events, version links) are NOT touched.
📑 Clone an existing project

Use one project's CMS as the starting point for a new one. Pick what to copy across. Numbers and contacts are usually project-specific, so they're unchecked by default.