Documentation
How Cisely works
The platform, explained in the order it makes sense to learn it — what the language expresses, how a design becomes a running system, and what you do with it.
Setup & Installation
Getting started with Cisely, which for most people means signing in: it runs in the browser, and Paroksh — the agent inside it — is ready the moment you arrive. The command-line tool and the connector for your own AI agent are here too, as the optional extras they are.
8 pages
Business Context Modeling
The other half of Cisely: who you serve, what they are reaching for, what you promise them, and how you know the promise was kept. A linked graph of intent rather than four documents that do not know about each other — so "why are we building this?" is answerable by following a link rather than by asking someone who was there.
8 pages
Introduction to Vishwakarma
The architecture expression language. Describe an enterprise system — its domain, rules, flows, and the systems they compose into — and the compiler checks the design and emits the running system from it.
7 pages
Business Process & Journey Modeling
The architecture overlay's demand side: the actors who use the product and the flows they walk. A business_process is one goal-directed flow; a journey composes whole processes into a per-actor arc. Each step states the capability it requires; the realizing system is derived, and gaps reconcile as a backlog in both directions. Every example is a real construct from the Chowk marketplace.
6 pages
System & Capability Modeling
The architecture overlay's supply side: the capabilities a product can do (the engineering primitives), the systems that provide them, the features that package them for consumption, and the UI surfaces that expose them. Every example is a real construct from the Chowk marketplace.
6 pages
Application Modeling
The buildable implementation, in layers. The domain layer models the business — aggregates, value objects, invariants, events. The application layer acts on it — commands, queries, sagas, subscriptions, policies. (The presentation and infrastructure layers follow.) Every example is a real construct from the Chowk marketplace.
25 pages
Building & Deploying
Turn a finished design into a running app: build it on the server, publish it (which deploys it), and reach the deployed API and web apps at their public URLs. Every command is real; the example is the Chowk marketplace.
1 page
Assurance
Your model makes claims — about who may read which rows, what must hold before a command runs, which errors an endpoint can return. Assurance derives every one of them as a checkable obligation and reports how many are actually backed by evidence, so an architecture description becomes a control rather than documentation.
5 pages