Engineering decision infrastructure

Keep the why
in the system.

Your codebase holds more than code. Arctyx turns the decisions and constraints behind it into cited, connected context—so the next change can be judged against what the system is meant to preserve.

Explore Arctyx See the decision graph
Built for teams already working with coding agents.
Gpayments / system graph
ILLUSTRATIVE VIEW  ·  08 OBJECTS
Constraint · Token lifetime: 15 min
Linked to the decision and source evidence that explain the rule.
systemdecisionconstraint DECISIONS  →  SYSTEMS  →  CHANGE
Context that survives the week
69%of developers lose 8+ hours each week to inefficiencies
2,100+developers surveyed in Atlassian's 2024 DevEx report
2025DORA found AI amplifies organizational strengths and weaknesses
Independent research, not Arctyx product results. Sources: Atlassian, 2024 · DORA, 2025
01 / The decision graph

Architecture tells you what connects.
Decisions tell you why.

The rules that keep production safe rarely live in one place. They are scattered across reviews, incidents, docs, and the people who remember. Arctyx is designed to give those reasons durable structure.

01 / Decision

Record what was chosen

Capture a decision as a durable object: its statement, status, owner, date, and the systems it affects.

02 / Evidence

Keep the source attached

Connect the reason to a source—such as a PR, review comment, document, test, or incident note.

03 / Constraint

Make the rule inspectable

Express the behavior that should hold, with a traceable path back to the decision behind it.

When someone asks “why is this service like this?”, the useful answer is a decision with evidence—not a confident summary without provenance.

See the graph in context
02 / Change review

A diff is not the whole story.

A PR can look plausible and still cross an invisible boundary. The intended PR context brief connects changed systems to relevant decisions and constraints, then makes a possible mismatch easier to inspect.

partner-auth / token-policy.ts PR #482  ·  illustrative review
REVIEW CONTEXT
@@ token expiry configuration @@
− const partnerTokenTtl = 15 * MINUTE + const partnerTokenTtl = 24 * HOUR issuePartnerToken(account, partnerTokenTtl)
Possible constraint conflict
Accepted decision: partner API tokens expire after 15 minutes. Source: PR #311, review thread, lines 42–58.
Context receipt / concept

Show the reasoning, not a verdict.

Reviewers need to see what informed a finding, what was touched, and where the evidence came from.

Systempartner-auth
DecisionShort-lived partner tokens
EvidencePR #311 · review lines 42–58
SignalDiff changes the stated lifetime
Product direction · roadmap
Illustrative example only. Not a live customer PR or product result.INTENT: CITE · SURFACE · LET A HUMAN DECIDE
03 / An accountable context layer

Useful context has to be reconstructable.

A system that influences code changes needs stricter rules than a chat window. Arctyx is built around durable objects, visible provenance, and human confirmation where inference is uncertain.

01

Source before assertion

Every answer should be traceable to evidence. If it cannot cite a source, it should not present a claim as fact.

↘
02

Inferred stays inferred

Candidate decisions remain visibly unconfirmed until a person with context accepts or corrects them.

↘
03

Permission is part of context

Evidence has access boundaries. Context should be assembled with those boundaries in mind, not waved away.

↘
04

History does not disappear

A superseded decision should remain legible as history, rather than silently rewriting what the team once agreed.

↘
Design invariantEvery answer to a person or agent should be reconstructable from cited evidence. No source, no assertion.
04 / Product, plainly

The graph is the product. The brief is one view.

Arctyx is being built as engineering decision infrastructure—not a code generator, a ticketing system, or another summary of what happened.

The product direction connects a decision graph to change review and, over time, to the agents that need system context before they edit.

Scope matters. The capabilities below distinguish the core product direction from work that remains on the roadmap.
Available

Decision graph

Manually record sourced decisions, connect systems and constraints, then confirm or reject proposals.

In the workspace
Available

PR risk brief

Paste a diff to check it against confirmed literal rules. Verified GitHub App repositories can also receive advisory, ID-only PR comments.

Manual or connected
In progress

Agent context & receipts

HTTP retrieval records what context was issued. Dedicated agent identity and MCP access remain planned.

HTTP available
Roadmap

Morning Pulse

A small daily projection of graph changes, open conflicts, and decisions that need attention.

Planned view

Roadmap labels indicate direction, not available functionality. Arctyx does not currently promise enforcement, native agent integrations, or enterprise deployment options.

An additional view

And yes, a morning pulse.

Useful as a projection of the graph: what changed, what conflicts, and where an owner is missing. It is not the product's center of gravity.

Decision needs an ownerIDENTITY / 2D
Possible constraint conflict in open changePARTNER API
System explanation has not been confirmedBILLING / 8D
The environment is changing

More generated code. Same human responsibility.

These are external industry findings, not outcomes achieved by Arctyx.

69%

of developers surveyed say they lose 8+ hours a week to inefficiencies. Tech debt and insufficient documentation are among their main complaints.
Atlassian State of DevEx, 2024

DORA
2025

reports AI amplifies an organization's strengths and weaknesses; AI adoption continues to be negatively associated with delivery stability.
DORA Report, 2025

Make the reasoning part of the system

Give the next change
a memory.

Start a conversation Or write to luxnvus@gmail.com Already have an account? Sign in