OscoArchitecture & decisions
Stop re-debating decisions you already made.
Systems keep the result of a decision but lose the reasoning. Osco keeps architecture docs, Mermaid diagrams and decision records next to the features and tasks they affect.
The problem
What gets in the way today
- Nobody remembers why a design was chosen, so it gets questioned again.
- Architecture diagrams are images that nobody updates.
- Docs are organised by who wrote them, not by the system they describe.
How Osco helps
Context that travels with the work
Decision records that are easy to find
Keep a decision log as a folder of docs, each with context, options, decision and consequences.
Diagrams as text
Write Mermaid diagrams inside Markdown so they are versioned with the doc and easy to change.
A feature graph
See how features connect to each other and to the docs, endpoints and tasks behind them.
Context for every change
Link a task to the decision it depends on, so the reasoning shows up before anyone codes.
How it works
From setup to everyday use
- 1
Write
Record the decision with the options you rejected and why.
- 2
Diagram
Add a Mermaid diagram of the design in the same doc.
- 3
Map
Link the doc to the features it affects in the feature graph.
- 4
Reference
Attach it to tasks so implementers and agents read it first.
Frequently asked questions
Does Osco support architecture decision records?
Yes. Any doc can be an ADR. Most teams keep them in a Decisions folder and link each one to the tasks and features it affects.
Can we render diagrams?
Yes. Mermaid code blocks in Markdown render as diagrams in the document.
Can we import existing Markdown?
Yes. Drop .md files or folders onto a project to import them with their structure.
More use cases
Give every task the context to finish it.
Start free with your team. Bring your Markdown, connect your coding agents and invite people when you are ready.