2026-08-18 12:05:11 +00:00
|
|
|
# arc-nexus
|
|
|
|
|
|
2026-08-21 22:22:00 +02:00
|
|
|
An architecture management service that acts as a central registry for
|
|
|
|
|
architecture blueprints, specifications, guidelines, documents, and ADRs.
|
|
|
|
|
|
|
|
|
|
## Interface evolution practice
|
|
|
|
|
|
|
|
|
|
Arc Nexus phases out old interfaces using the InfoTechCanon
|
|
|
|
|
`InterfaceDeprecationStrangler` PracticePattern.
|
|
|
|
|
|
|
|
|
|
- Canon artifact ID: `practice-pattern/interface-deprecation-strangler`
|
|
|
|
|
- Canon source:
|
|
|
|
|
`info-tech-canon/infospace/patterns/InterfaceDeprecationStrangler.md`
|
|
|
|
|
- Scheme: `practice-pattern/0.1`
|
|
|
|
|
|
|
|
|
|
For an Arc Nexus interface, adoption means that we name and verify its
|
|
|
|
|
successor, communicate deprecation and the successor at the legacy boundary,
|
|
|
|
|
meter privacy-bounded caller use, distinguish successfully served legacy
|
|
|
|
|
traffic from rejected post-retirement attempts, retain an observable tombstone
|
|
|
|
|
after behavior is retired, and remove that tombstone only after the evidence
|
|
|
|
|
gate passes.
|
|
|
|
|
|
|
|
|
|
An intended adoption is not implementation evidence. Each concrete Arc Nexus
|
|
|
|
|
use must identify its interface registry record, meter, lifecycle stage,
|
|
|
|
|
retirement policy, and review evidence.
|
