Jason Dijols
← All work

Gauntlet AI · 2026

Colign

Open-source weekly planning where every commitment links to strategy

Screenshot of ColignScreenshot of Colign
Role
Solo builder: full stack, brand, open-source release
Timeline
1 week (ST6 Partners brief), ongoing
Stack
Spring Boot 3.3JavaVite 5 Module FederationReactAuth0 OIDCPostgreSQL 16

The problem

Weekly planning tools like 15-Five collect what people plan to do, but nothing connects those plans to company strategy. Employees write check-ins into the void; managers can't see whether the week's work supports the right priorities until quarters later. The ST6 Partners brief asked for a production-ready micro-frontend module to replace 15-Five.

The approach

Colign makes alignment a precondition instead of an afterthought: every weekly commit carries a structural foreign key to a leaf Outcome in the Rally Cry → Defining Objective → Outcome hierarchy. Managers get a roll-up showing high-priority alignment percentage, the share of each report's commits linked to a P0/P1 outcome, so drift is visible the week it happens. The module ships as a Vite Module Federation remote consumed by a host shell, with a Spring Boot API, Auth0 OIDC, and Postgres behind it. After the submission, I kept going: custom monochrome brand, MIT license, and an open-source release at colign.org.

The hard parts

Micro-frontend architecture for real

The brief demanded a Module Federation remote that drops into a host shell. Getting auth, routing, and styling to behave identically standalone and embedded required a disciplined seam between module and host.

Making alignment structural, not aspirational

The core design decision: the link from commitment to outcome is a database constraint, not a suggestion. You cannot save a weekly plan that doesn't map to strategy, which forces the conversations that matter.

Submission and open source coexisting

Rather than maintain a fork, the repo preserves the brief's submission flavour and layers the open-source identity on top: two audiences, one codebase, no contradiction.

Where it landed

Shipped the brief end-to-end, then released it as a real open-source product at colign.org with its own brand system. Every AI-assisted decision was logged per the brief's documentation requirement.

Next project

Vast Media