Signed In As
Every generation request below is checked server-side against
YOUR real account's role (authorization.js's capability table) --
not anything this page displays or could be made to display. Ask
an administrator to provision an account via
runtime-validation/scripts/createUser.js if you don't
have one yet.
1. Estate
The user supplies real business attributes; Kosarix generates the canonical EstateCode (derived from the Estate name's initials, then disambiguated) — never typed by the user (governing directive §6). An Estate is the master land container — everything below (Land and Projects) belongs to a real, existing Estate.
LAND — Estate's own land, unconditional
2. Land Block Generator
Not ordinary CRUD — bulk, authorized, previewed before commit. A Land Block belongs to its Estate directly. No Cluster Code. No Project Code. No manually typed Block Code — Kosarix generates it.
3. Plot Generator
A Plot must belong to a Land Block belonging to the selected Estate — cross-Estate generation is rejected. No Project field — a Plot's relationship to a Project (if any) is established later, explicitly, via Project Land Allocation.
4. Plot Subdivision Generator
Exceptional, not routine: subdivides one existing Plot into smaller
child parcels with Kosarix-generated codes derived from the parent
(e.g. PH-BLK-I-001-A). The parent Plot remains in the
land registry as the parent parcel but its own Status flips to
"Subdivided" and it can no longer be independently allocated while
its children are active — allocate the specific Subdivisions
instead. A Plot already allocated to a Project cannot be subdivided;
a Subdivision cannot itself be subdivided again.
PROJECTS — developments situated on a portion of the Estate's land
5. Project
Kosarix generates the canonical ProjectCode from the Project name you supply, the same way it generates EstateCode — never typed by the user. A Project must belong to a real, existing Estate. A Project does not own Land — see "Land Allocation" below.
6. Project Land Allocation
A Project references existing Estate land — it never creates new land, and a Block/Plot/Subdivision is never duplicated. Select a single Plot, several Plots in one Block, an entire Block, several Blocks, individual Plot Subdivisions, or any mix. A Block/Plot already allocated to another Project cannot be selected again; a subdivided Plot's own parent cannot be selected while its children are active (allocate the Subdivisions instead — see ADR-0018); cross-Estate allocation is rejected server-side.
7. Project Development
A Project's own structure — Building Blocks and their Units — is separate from, and unrelated to, the land track's Block/Plot concept above. Reuses the real Kosarix Building/Unit master data.
Building Generator
Unit Generator
Generation History
Every batch below can be inspected before it is touched. A batch that has not already been rolled back and succeeded (Status "Success") can be reversed via Rollback Batch — Kosarix checks every generated record for real downstream dependencies first, and either reverses the entire batch or reverses nothing at all, never a partial rollback. The original history row is never deleted, even after a successful rollback — only its Rollback Status changes.