GenCMS is iGears' model-agnostic AI workspace and runtime direction for building assistants, document extraction, content and internal agent solutions on an organisation's own data.

It is for developers and organisations that need custom or privately deployed AI with explicit tenant, data and permission boundaries.

Account and tenant administration, workspace records, scoped API keys and Guard scanning are available. Composer can run through a tenant's region-locked AIHK or AICA gateway after its AI key is ready.

Request managed workspace access or ask iGears to scope a 30-day MVP. Project services are fixed-price, with the scope, fee and acceptance checks stated in a quotation.

Memory — Docs

Memory

Collections, what goes in them, and how retrieval reaches a run.

Availability note — these docs describe both working and planned product areas. Account authentication, administrator-managed AIHK/AICA tenant regions and keys, signed-in Composer runs and public Guard scans are connected. Skills, Memory, Agents, Workflows, Apps, billing, the public SDK/CLI and the unified API are previews unless a section explicitly says otherwise.

Roadmap and package-contract reference: this page describes the intended GenCMS runtime. The current deployment persists workspace records and drafts but does not execute marketplace Skills, index Memory for retrieval, publish packages, or run Agents, Workflows or Apps. See the deployed API reference for the routes available today.

Memory is where a workspace keeps what its AI should already know. It is organised as collections so access can be granted per Agent, per Skill and per run rather than all at once.

Workspace
├── Knowledge
│   ├── Documents      PDF, DOCX, Markdown, uploads
│   ├── Websites       crawled URLs, re-indexed on a schedule
│   ├── Repositories   connected Git repositories
│   └── Notes          pasted text
├── Memory
│   ├── Conversations  prior runs worth keeping
│   ├── Decisions      what was chosen and why
│   ├── Project state  where something currently stands
│   └── Summaries      learned condensations of long material
└── Rules
    ├── Brand          tone, terminology, prohibited claims
    ├── Coding         standards, review expectations
    ├── Compliance     what must always be stated or avoided
    └── Output         preferred formats and structures

Every item carries its provenance

Title, source and type
Which collection and workspace it belongs to
Created date and last indexed date
Permission level
Which Apps and Agents are connected to it
Export and delete controls
Whether source citation is available for it

That last field matters most. When an answer comes back you can ask where it came from, and GenCMS returns the source references it retrieved rather than a claim that it knew.

← PreviousVersioning and updates Next →Adding sources