mc.
Michael CunninghamSOFTWARE + AI ENGINEERING
PortfolioLet’s build
00 / 04
+ INDEPENDENT MIND. ORGANIZATION-SCALE THINKING.

Complexity,
engineered.

I build the interfaces, the systems behind them,
and the intelligence that connects the work.

AN INTERACTIVE EXPLORATIONFour chapters.
One engineering mind.
Selected work
01 / ARCHITECTUREOPEN THE SYSTEM

Below
the surface.

The interface is the part you see.
The architecture is what makes it hold.

LAYER 03

The human layer

Custom desktops. Rich editors. Components that carry their own behavior—and compose into something larger.

React
TypeScript
MUI
Tiptap
Explore my complete stack
INTERFACE / SERVICES / DATA
01.B / THE CONTRACT BENCH

Trust the boundary.
Test the consequence.

Follow one assignment beneath the interface. Inspect its intent, challenge its authority, then examine the exact write set.

LOCAL REHEARSAL / NO NETWORKNorthstar Studio REV 1

Use the customer, role and records currently selected in Connected Work.

Isolated copy. Your working records stay unchanged.
INSPECTION OUTCOMEReady to interrogate.

Select a condition and run the same assignment rules used in Connected Work.

INTERFACE / CONTRACT DETAIL

Intent is a snapshot, not a blank cheque.

command
asset.assign
customerId
497f6eca-6276-4993-bfeb-53cbbbba6f08
assetId
7c72bef2-4bd7-4217-b6cd-c428b2b511be
expectedRevision
1

Customer, asset and revision travel together. A later change cannot silently rewrite the intent that was reviewed.

In-memory behavior study. Not a live API or production authorization system.
02 / CONNECTED WORKONE ACTION. EVERY CONSEQUENCE.

Nothing works
in isolation.

CRM. Projects. Inventory. One shared context.
Make an assignment and watch the records move together.

CONNECTED WORKSPACELOCAL SAMPLE
NS
Alex MorganAssignment recipient
asset.assign granted
Available inventory
CustomerNorthstar Studio
Inventory3 assigned
Project1/4 complete
READY WHEN YOU ARE

Choose an available device.

Review the customer, recipient, and connected project update before committing an assignment.

ACTIVITY / REVISION 1

Your first committed action will appear here.

Fictional records · No endpoint execution · Changes stay in this page
03 / APPLIED INTELLIGENCECONTEXT. JUDGMENT. ACTION.

Intelligence.
With intent.

AI belongs inside the work.
With the right context, a reviewable change,
and a boundary it cannot quietly cross.

01 / ASSEMBLE CONTEXT

The system remembers.

CNorthstar StudioCustomer context · included

Prepared example · No live model call. The context and document changes are real local state.

02 / REVIEW THE CHANGE
Project brief / proposed addition
“

Your customer, inventory, and project state become a reviewable handoff.

Choose context. Prepare. Inspect. Decide.
04 / INSIDE THE INTERFACELESS WATCHING. MORE DOING.

Step
inside.

The architecture becomes something you can use.

Move a window. Open a customer. Work the project board. Edit the brief. Your changes from the previous chapters are already here.

Desktop shellCustom componentsRich authoringShared records
04.A / INTERFACE OBSERVATORY

One system.
Four working lenses.

The same customer, project, inventory, and document state—seen through the interface each decision needs.

CUSTOMER SYSTEM / LIVE LOCAL CONTEXT

Context before action.

Current context
Northstar Studio
Primary contact
Alex Morgan
Record revision
01
04.B / LIVE APPLICATION SURFACESHARED SESSION / NORTHSTAR STUDIO / READY
mc.

The working studio opens as you arrive.

WINDOWED WORKSPACE / POINTER + KEYBOARDLOCAL RECORDS / NO REMOTE EXECUTION
These are interactive recreations of application patterns from my work.Open the standalone showcase