GenCMS Memory

Teach it once. Use it everywhere.

Create tenant-scoped collections and store supplied text or source records now. GenCMS does not fetch, parse, index, retrieve or cite those sources yet.

Available now

Persistent collection records, supplied text and source metadata.

Preview

Planned: fetching, parsing, indexing, retrieval, citations, collection grants and export.

Concept illustration of approved sources and rules entering a layered Memory store; retrieval remains planned

The context model

Knowledge + Memory + Rules = Context.

Three collection types are available for organising records. Their different retrieval-time behaviour remains a product design, because retrieval is not implemented.

Knowledge

Explicit information represented by source records you supply.

See examples
  • PDFs and DOCX
  • Webpages and manuals
  • API documentation
  • Git repositories
  • Policies and FAQs
  • Notes

Memory

Planned information a future runtime could retain through use.

See examples
  • Previous decisions
  • Conversation history
  • Project state
  • Useful summaries
  • Successful approaches
  • Prior task outcomes
§

Rules

Stored standing instructions; automatic run-time application is planned.

See examples
  • Brand tone
  • Coding standards
  • Company terminology
  • Prohibited actions
  • Compliance rules
  • Preferred formats

Company workspace

  • Brand Guidelines
  • API Documentation
  • Product Website
  • Git Repository
  • Project Decisions

GenCMS Memory

Knowledge + Memory + Rules = Context

Skills
Agents
Workflows
Apps

Sources

Store source records today; indexing comes next.

Save supplied text or a reference to a URL, file, repository or structured item. GenCMS stores the record but does not fetch, upload, parse, index, embed, refresh, retrieve or cite it.

Store text

Save text you supply directly with the source record.

Record URL

Keep the URL as a reference; it is not fetched or crawled.

Record file

Keep file metadata; the referenced file is not uploaded or indexed.

Record repository

Keep a repository reference; it is not cloned or searched.

In your workspace

Everything about a collection on one page.

See persistent collection and source records, their status and recorded changes. Usage, retrieval results, costs and citations are not available.

Collections

Organise tenant-scoped knowledge, memory and rules records.

Sources

Keep text, URL, file, repository or structured source records. Retrieval and citations are not available.

Activity

Record collection and source changes when workspace activity recording is enabled.

Draft references

Connect intended collections to Agent and Workflow drafts without claiming runtime retrieval.

Access

Planned collection grants.

The intended model separates read and write grants for each Skill, Agent or Workflow. Those grants are not enforced by a runtime today.

memory.readmemory.writeCollection-scopedRevocableAudited

Planned access model — collection records are tenant-scoped, but per-collection grants, retrieval auditing, execution-time permissions and export are not implemented.

Read

Limit a future run to approved collections.

Write

Keep updates separate from retrieval access.

Audit

Record which context a future run used.