Archify Software Topology & Architecture Visualizer

@tt-a1i/archify · v2.0.4

An automated architecture reverse-engineering engine transforming source code and schemas into clean Mermaid, PlantUML, and C4 model diagrams with drift detection.

ArchitectureMermaidC4-ModelAST-Analysis
GitHub Stars
72 K+
+12.4% this month
Monthly Downloads
285 K+
Monthly registry pulls
Reach Score
99.4/ 100
Top Tier Ecosystem
Runtime
Cordis v3+
Node 18+ / Bun / Deno

Installation & Integration

CLI one-click launch, package managers, and Cordis integration

bash
manager:
$ pnpm add @tt-a1i/archify

Architecture

Archify brings immediate clarity to complex software systems. In fast-paced engineering environments, architectural diagrams decay rapidly, drifting away from the true codebase implementation. This plugin leverages AST analysis and dynamic trace sampling to reverse-engineer microservice relationships, module imports, and relational schemas. Outputting clean Mermaid, PlantUML, and C4 diagrams, Archify embeds into CI pipelines to keep developer documentation permanently aligned with actual code.

Architectural Principles & Constraints

01
Strict Type Isolation

Guaranteed by TypeScript compile-time contracts, inter-plugin event bus calls enjoy zero-drift safety.

02
Sub-Millisecond Hot Reload

Supports dynamic runtime mounting and graceful unloading without restarting the primary host process.

03
Deterministic State Machine

Embeds multi-phase execution lifecycle guards, preventing context loss during long-horizon reasoning.

04
Zero Native Build Dependencies

Designed for lightweight cross-platform environments, booting instantly across Node.js, Bun, and Deno.

Core Features

01
C4 Model Native: Supports top-down drill-downs across Context, Container, and Component levels
02
Dual Syntax Engine: Exports compliant Mermaid, PlantUML, and high-DPI vector assets
03
Circular Import Detector: Flags tight couplings and dangerous cyclical dependencies in source
04
PR Architecture Diff: Visualizes architectural changes and boundary violations in pull requests

Core Workflow

01

Dependency AST Extraction

Scans repository ASTs to extract package dependencies, class models, and RPC routes.

02

Hierarchical Graph Modeling

Builds C4-compliant context, container, and component graphs from dependencies.

03

Syntax Generation

Optimizes layout routing and compiles valid Mermaid, PlantUML, or raw SVG vectors.

04

Doc Sync & Drift Check

Updates README wikis and alerts engineers if circular dependencies are detected.

Configuration Parameters Reference (YAML / JSON)

ParameterTypeDefaultDescription
diagramTypestringmermaidOutput diagram format
depthLevelnumber3AST parsing dependency recursion depth
detectCyclesbooleantrueEnable circular dependency scanning and warnings

Use Cases

Enterprise Production Agent

Relies on microkernel lifecycle guards and fault-tolerant state machines for continuous reliability.

SWE-bench Benchmark Evaluation

Native integration with SWE-bench workflows, automatically capturing diffs and verification metrics.

Autonomous Code Refactoring

Separates reasoning from tool actions to independently locate and refactor multi-file codebases.

Cross-Tool Workflow Automation

Safely orchestrates events across sandboxes to seamlessly link enterprise developer tooling.

Best Practices

01
Sandbox Permission Guard

Strictly isolate sub-process calls and network scope; deploy within Docker containers in production.

02
Exponential Backoff Retries

Configure adaptive exponential retries with strict timeouts to mitigate upstream model rate limits.

03
Session State Checkpointing

Persist state machine snapshots to survive hardware interruptions and resume instantly without loss.

04
Full Trajectory Audit Logs

Enable full trace logging, aggregating reasoning thought streams and tool I/O into your observability hub.

FAQ

Q1:How to handle timeouts in long-running autonomous tasks?

Increase the timeout parameter inside your YAML configuration and dispatch periodic heartbeat signals across the Cordis event bus. For long-running tool execution and model reasoning, configure persistent session snapshotting so suspended tasks can safely resume their exact context after interruptions, preventing the kernel from recycling active agent sessions prematurely.

Q2:How to capture and stream the model reasoning thought process?

The harness runtime natively provides end-to-end streaming hooks while its state machine automatically intercepts and strips <think> reasoning tags from model responses. Subscribe directly to the onThink event listener to consume live reasoning token streams in real-time, delivering typewriter animation to the user interface while persisting full trajectories for audit compliance.

Q3:How to resolve dependency conflicts across multiple plugins?

Cordis microkernel uses directed acyclic graph topological sorting to dynamically resolve plugin dependencies. When shared services or runtime versions conflict, assign distinct isolated namespaces at the application entrypoint. Leveraging context injection alongside lazy activation ensures dependencies load strictly on-demand when tools are triggered, maintaining system stability and preventing memory bloat.

Q4:How to enforce permissions and sandbox isolation in production?

Combine isolated container sandboxing with fine-grained capability checks to prevent plugins from accessing sensitive files or unauthorized external networks. Enforce explicit runtime system call whitelisting through the microkernel, executing all third-party tool scripts inside isolated ephemeral containers to block arbitrary code execution and eliminate security privilege escalation risks entirely.

Recommended Ecosystem Plugins

Explore related Cordis extensions designed to work synergistically