Xtrable
The most expensive moment in any architecture is the change you make without knowing what depends on it. A renamed field, a tightened type, a retired entity, and three teams downstream find out in production. NeoArc is built so that moment does not happen.
Lineage that is always live
As you wire a model property onto a database column, a schema field, or an API token, NeoArc records the connection. Those connections form a continuous chain: an API token traces back through a schema field, to a database column, to the model property it all started from. The chain is not a comment you maintain by hand. It is the wiring itself, so it is always current.
Ask what breaks, before you break it
Because the lineage is explicit, NeoArc can trace it in both directions:
- Upstream: where does this field's data actually come from? Follow any column or token back to its origin in the model, across as many hops as it takes.
- Downstream: if I change this property, what depends on it? See every database, schema and API that draws from it, grouped so a wide blast radius reads as "three databases", not thirty rows.
A checkpoint, not a surprise
When you rename, retype or delete something other things depend on, NeoArc does not let the change slip through silently and it does not simply block you. It pauses, shows you the impact, and offers a clear choice: cancel, apply now and track the catch-up, or plan a coordinated migration. Change is normal. Unseen change is the problem NeoArc removes.
Drift is caught and named
When the model moves and a projection has not caught up yet, NeoArc flags exactly where, and tells you why: a field was renamed, a type changed, something was deprecated. You resolve it deliberately, with one action, rather than discovering it later as a mysterious mismatch.
Impact analysis stops being a manual audit measured in weeks and becomes a structured query measured in seconds. That is the difference between hoping a change is safe and knowing it.