Governed software production.
From documentation to working code.

Describe requirements, architecture, business rules, test scenarios, configurations — as interconnected documents in language the whole team understands.

## User Authentication

The system **shall** authenticate users
via OAuth 2.0 with PKCE flow.

Session timeout: 30 minutes.
Max concurrent sessions: 3.

Docency builds a dependency graph between documents. Every artifact — from requirement to test — has known connections. A change in one place is visible across the entire system.

auth.md
├── api-routes.md
├── db-schema.md
└── middleware.md
    └── rate-limit.md

Change a requirement — Docency identifies every document and artifact that depends on it and propagates context-aware updates through the entire graph. Code, tests, configuration — everything updates.

auth.md           [changed]
├── api-routes.md  [updated]
├── db-schema.md   [updated]
└── middleware.md   [updated]
    └── rate-limit.md [updated]

The NL-to-code compiler generates source code, tests, configurations, APIs, data schemas — everything linked to source documentation. Documentation IS the source code.

export async function authenticate(
  req: Request
): Promise {
  const token = await verifyPKCE(req);
  return createSession(token, {
    timeout: 30 * 60,
    maxConcurrent: 3,
  });
}

The system detects missing information and inconsistencies. People verify and decide. Every change is tracked — full audit trail. Post-deployment: logs, error observation, fix propagation.

auth.md           [ok]
├── api-routes.md  [ok]
├── db-schema.md   [warning: missing index]
└── middleware.md   [ok]
    └── rate-limit.md [ok]
audit: 12 changes tracked