Cortex Neuron — Matriculation

Staff: Open the enrollment dashboard → (sign-in required; staff/admin only)

The post-acceptance task tracker. Once a prospective student is accepted, a small set of matriculation tasks (deposit, FAFSA, transcript, housing, and the rest) needs to get done before they enroll. This neuron is the system-of-record for those tasks. Phase 1 runs in parallel with HubSpot as a shadow / dry-run: it observes the live acceptance trigger and logs the Cortex action that would fire— without firing it — so the would-fire log can be compared against the real HubSpot board before go-live. Going live is a single environment flip (MATRICULATION_DRY_RUN=false), not a code change. Phase 1 is HubSpot → Cortex observe-only: nothing is written back to HubSpot.

Things you can ask Claude

• “Show me the matriculation shadow log for the last week.”
• “What tasks would have been created for this accepted student?”
• “Are we live yet, or still in shadow / dry-run mode?”
• “Re-run the shadow observation for this deal.” (admin)

During Phase 1 these read the would-fire shadow log, not live matriculation tasks — they stand in for the live task list until the flip and the backlog seed land.

Tools

• get_shadow_log — recent shadow runs and the matriculation tasks each acceptance would have created. Phase 1 reads the would-fire shadow log, not live matriculation_task rows. (admin or staff)
• get_matriculation_status — runtime mode: whether the neuron is in dry-run or live, which sink is active, last observe time, and would-fire / created counts. Ask this to find out “are we live?” (admin or staff)
• replay_shadow_event — re-observe a single acceptance event by its HubSpot deal id. Bounded: respects the current dry-run / live mode, so it can never accidentally force a live write. (admin only)

Who can see what

The shadow log and status are available to any admin or staff member; the replay tool is admin only. Every call is audited with the justification you give. This neuron handles FERPA-shaped student data, so there is no anonymous access — each call records who asked, what they asked for, and why.

If Claude says you’re “not authorized,” your Cortex role doesn’t include that tool yet — ask IT to provision the right role for you.