Ligatrix Methodology

Public delivery method for Ligatrix work.

This repository explains how Ligatrix turns a business problem into a scoped, usable internal tool or workflow system, with checks that can be reviewed later.

Core Loop

1. Vision - define the business problem and the useful outcome.
2. Context - map users, workflows, systems, data, and constraints.
3. Audit - inspect the real source of truth before proposing changes.
4. Contract - write acceptance criteria and non-goals.
5. Plan - choose the smallest durable path.
6. Implement - build inside the verified boundary.
7. Verify - test against the actual acceptance surface.
8. Review - inspect the result, risks, and tradeoffs.
9. Handoff - preserve what was done, how it was checked, and what remains.

Principles

• Build real systems, not demos that only pass one screenshot.
• Preserve client ownership and avoid unnecessary platform lock-in.
• Keep client and product source private unless publication is explicitly intended.
• Treat proof of work as part of the deliverable.
• Prefer narrow, inspectable milestones over large ambiguous rewrites.

Contents

• Delivery method
• Project contract template