APD — AI-Powered Development

Šta ne radi u klasičnom razvoju. What doesn't work in classic development.

Sporo Slow

Veliki timovi. Mnogo ručnog rada. Broj ljudi određuje učinak. Big teams. Lots of manual work. Linear relation between headcount and output.

Dugi ciklusi Long cycles

Skupo Expensive

Senior inženjeri pišu boilerplate. Znanje zarobljeno u glavama. Operativni trošak raste. Seniors writing boilerplate. Knowledge trapped in heads. Operational cost compounds.

Visok fiksni trošak Expensive overhead

Krhko Fragile

QA kao ljudski gate. Kvalitet zavisi od toga ko je i kada pregledao. QA as a human gate. Quality depends on who reviewed it and when.

Stalne prepravke Frequent rework

Specifikacija je merilo svega. Sve ostalo prolazi kroz gate. Spec is the source of truth. Everything else clears the gate.

APD spaja AI agente, specifikaciju koja se ne menja u hodu i automatske gate-ove. Pipeline ima pet koraka — spec, builder, reviewer, adversarial, verifier. Svaki može da blokira commit kad nešto ne odgovara. APD pairs AI agents, a frozen spec, and automatic gates. The pipeline runs five steps — spec, builder, reviewer, adversarial, verifier. Any of them can block the commit when something doesn't match.

APD · 4-layer pipeline

Gde je razlika. Where the difference is.

Tradicionalno Traditional

Više ljudi = više učinka. Linearno. Headcount = output. Linear scaling. Dodaješ ljude da bi išao brže. You add people to go faster.
Ručni rad dominira. Manual work dominates. Seniori pišu boilerplate. Seniors write boilerplate.
Znanje živi u glavama. Knowledge lives in heads. Bus factor = 1. Bus factor = 1.
QA kao ljudski gate. QA is a human gate. Regresija je česta. Verifikacija subjektivna. Regressions are common. Verification is subjective.

APD

Učinak dolazi iz sistema. Nelinearno. Output comes from the system. Non-linear. Mali tim pokreće celu platformu. A small team runs the whole platform.
Generisanje iz verifikovanog modela. Generation from a verified model. Ti pišeš spec. Ostalo generiše pipeline. You write the spec. The pipeline generates the rest.
Znanje kodifikovano u sistem. Knowledge codified in the system. Arhitektura je zapisana i proverljiva. Architecture is written down and checkable.
Automatska verifikacija kao gate. Automated verification as the gate. Ako invarijanta padne, isporuke nema. If an invariant fails, nothing ships.

Četiri bloka koja čine sistem. Four blocks that make the system.

01 · Spec

Jedno merilo Single source of truth

Spec-card sa R* kriterijumima prihvatanja. Hash se zaključava na startu pipeline-a — svaka izmena ga ruši i blokira napredak. Spec-card with R* acceptance criteria. The hash locks at pipeline start — any edit breaks it and blocks progress.

.apd/pipeline/spec-card.md

02 · Guard

Zaštita je kod The guard is code

Pravila su ugrađena u skripte. Builder ne može pisati van svojih granica, orchestrator ne može commit-ovati pre verifier-a, git nema mass staging. Rules live in scripts. The builder can't write outside scope, the orchestrator can't commit before the verifier, git can't mass-stage.

apd doctor

03 · Pipeline

Svaki korak ima gate Every step has a gate

Spec → Builder → Reviewer → Adversarial → Verifier. Korak ne prelazi dok prethodni nije HMAC-potpisan. Spec → Builder → Reviewer → Adversarial → Verifier. A step doesn't advance until the previous one is HMAC-signed.

apd pipeline status

04 · Report

Trag kroz svaki run Trace across every run

Pokrivenost spec-a, vreme po koraku, blokade gate-ova, trend uspešnosti — sve u jednom izveštaju. Spec coverage, step durations, hook blocks, success trends — all in one report.

apd report --history

~30–50%

Kraći ciklus isporuke kroz projekte građene na APD-u. Shorter delivery cycle across projects built on APD.

Distribucija kroz 10+ projekata · medijan 45% · zavisi od obima i domena Distribution across 10+ projects · median 45% · varies by scope and domain

Delivery cycle

Za trećinu do pola A third to a half

vs. tradicionalni pristup, kroz projekte u produkciji. vs. traditional approach, across production projects.

Team size

Manji tim Smaller team

Isti obim posla sa manje senior inženjera. Same scope with fewer senior engineers.

Production

Stabilno Stable

Aktivni SaaS sistemi u svakodnevnoj upotrebi. Live SaaS systems in daily use.

Regen-to-ship

Minuti Minutes

Od izmene spec-a do deploy-a. From spec change to deploy.

U svakodnevnom pogonu. Not an experiment.

APD pokreće SaaS platforme, enterprise sisteme i sopstvene proizvode. Evo gde tačno. APD powers SaaS platforms, enterprise systems, and our own products. Here's where.

SaaS

Sertifikovana eFiskalizacija (SaaS) Certified eFiskalizacija SaaS

Live, multi-tenant, sa sertifikatom regulatora. Svakodnevna upotreba kroz mrežu klijenata. Live, multi-tenant, regulator-certified. Daily use across the client network.

Sertifikat regulatora Regulator-certified

Enterprise

Enterprise loyalty platforme Enterprise loyalty platforms

Bambi, Generali, Lilly — jedna platforma za sve kanale. Bambi, Generali, Lilly — one platform across every channel.

3 enterprise brenda 3 enterprise brands

Internal

Sopstveni proizvodi Our own products

Brite. Naš brend, isti sistem kao za klijente. Brite. Our own brand, same system we use for clients.

Ideja → live, brzo Idea → live, fast

Platform

Loyalty platforma Loyalty platform

Platforma u celini izgrađena kroz APD. Aktivni enterprise klijenti. Platform built end to end on APD. Active enterprise clients.

U produkciji In production

Open source Open source

Jezgro je javno. Zajednica ga koristi. The core is public. The community uses it.

Otvoreni kod pod MIT licencom. Radi sa Claude Code i OpenAI Codex razvojnim okruženjima. Aktivan razvoj. Open source under MIT. Works with Claude Code and OpenAI Codex environments. Actively developed.

apd.run ↗

v7.0

Current release

MIT

License (core)

AžuranMaintained

Development

TS · PY · Go

Targets