Work
Management system first. Software second.
We move forward in versions. Each leaves something that works and something learnt. Today we are in the first.
What this folder holds
Source in the workspace: work/roadmap/
Five versions. From understanding the company to proving the system serves others.
V0We are here
Foundations
The theory, the shared language, the governance model and the method, before building.
- Review of prior work
- Business ontology
- Governance and autonomy model
- Acceptance criteria
V1
Know AKRIBIS
Catalogue the systems, the data owners and the documents, and bring them into one coherent model. The survey has already started, read-only.
V2
Structure and coordinate
Processes that are documents today become governed objects. Inconsistencies across systems are detected, and people approve the actions.
V3
Evolve and optimise
Architecture recommendations, capability migration and coordination with bounded autonomy, with measured results.
V4
Prove it elsewhere
Independent organisations use it, each isolated and with its own configuration.
Two tracks, in this order. Management leads; software follows.
Track A · Management system
How the company is directed, coordinated, run and improved. It has to work with people, documents, meetings and the tools that already exist, before any artificial intelligence.
Track B · Software
Translates into software what track A has validated. It can reveal practical limits early, but it does not dictate the theory.
We learnt it: a system built before the company is defined ends up copying what exists, defects included.
Six workstreams. Each on its track.
Theory and research
What the evidence says about strategy, management and coordination.
Management system
Purpose, choices, governance and method.
Enterprise architecture
Capabilities, processes, data and systems, as they are and as they should be.
Software platform
The core, coordination, intelligence and isolation between organisations.
Validation at AKRIBIS
All of the above, tested in the company itself.
Product evolution
How what works becomes something others can use.
And then: businesses that execute a system. First AKRIBIS, then our customers, then new businesses.
AKRIBIS, the first organisation
We use it at home first. An internal problem becomes an internal solution, is validated and turns into a reusable capability.
Our customers
They would manage their operation from strategy down to the calibrated instrument.
New businesses
Designed from the start as a working system: strategy written, operation configured, sensors connected.
The loop
- Operate
- Learn
- Standardise
- Productise
- Deploy
and learn again
Source in the workspace: system/docs/decisions/work/WORK.mdwork/DECISIONS.mdwork/decisions/work/log/
What we decided, and why. With its date and where its record lives.
The decisions that steer the work, with their date and where their record lives. The most recent first.
The directory is arranged by what you look for, not by when it was made.
Five folders, one per question: why, the company, the system, the work and the archive. What belongs to AKRIBIS stays apart from what serves any organisation. This site's menu is that directory.
Record:
work/decisions/WS-0001All the work is oriented to the Integrated Strategy Architecture.
Every piece is placed on the frame: its layer, its level, its stage of the cycle and its track. What is approved is the orientation; each design remains a proposal.
Record:
system/docs/decisions/ADR-0003This site starts telling the reasoning.
First on a single page; now with the working directory as its menu, one page per folder.
Record:
akribis_group/docs/narrative.mdFor near-term operations, we start from the sales system we already use.
Federate before replacing: what exists is improved before anything new is built. The direction is approved; changes in production are not yet.
Record:
system/docs/decisions/ADR-0002The research has its evidence base, with each organisation isolated from day one.
Sources, observations and their limits are kept with their provenance. Isolation between organisations is designed now, even though the others arrive later.
Record:
system/docs/decisions/ADR-0001Top management is a management committee appointed by the Board.
The management system's decisions have an explicit, collective owner.
Record:
company/2-management-system/decisions/0003ISO 9001 is the backbone, and the management system is built as a product.
AKRIBIS is its first user: what works here may serve others.
Record:
company/2-management-system/decisions/0001
Every decision has the options considered, its reasons and who approved it. Nothing is deleted: a superseded decision stays marked as such, next to the one that replaces it. The decisions that steer the work appear here; the detailed ones stay in their records.