Source References

When Rekhic generates an architecture diagram from source code, manifests, or README files, it attaches source references to the resulting nodes.

Why Source References Matter

In traditional diagramming tools, a box labeled Order Service has no traceability to the underlying codebase. Over time, as code evolves and names change, diagrams become stale and disconnected from reality.

By attaching source references:

• Engineers reviewing a generated diagram can immediately see which file or manifest triggered the component's creation.
• A database node indicates whether it was discovered via docker-compose.yml, a Prisma schema (schema.prisma), or dependencies in package.json.
• A microservice node links back to its entry point (e.g. src/server.ts or Application.java).

Inspecting References on the Canvas

When you click on a generated architecture node:

1. Open the node details in the context toolbar.
2. The Source Reference property displays:
   • File path (e.g. docker-compose.yml:L12 or package.json:dependencies).
   • Detection reason (e.g. Manifest dependency: redis).
   • Inferred component role.

Next: Learn how to generate Markdown specifications in Diagram to Documentation.