---
title: Documentation Updates
description: >-
  Documentation notes dated October 19, 2026, on the scope and functional limits
  of GovFrame.
audiencia: 'Users, governance leads, and administration teams'
roles: >-
  User | Data Steward | Data Owner | Data Engineer | Administrator |
  Superadministrator
modulo: Cross-cutting documentation
revision: '2026-10-19'
section: empezar
order: 40
sources:
  - CONTEXT.md
  - ARCHITECTURE.md
  - TESTING_GUIDE.md
  - Modelodeobjetosyrelaciones.md
  - Módulosydependencias.md
  - 'Roles,capacidadesyalcance.md'
  - Cómoleerelmapaderelaciones.md
locale: en
---
# Documentation Updates

This page brings together **documentation notes** dated **2026-10-19**. It is not a service version history and does not confirm a feature release. Each note clarifies the behavior and limits that public documentation must reflect.

## 2026-10-19 — Context and relationship model clarified

The taxonomy is documented as a navigation axis in its two available forms: Domain → Entity → Attribute and Domain → Subdomain → Entity → Attribute. It was clarified that relationships can be direct, through a component, inherited, or derived through composition. Sharing a Domain is not enough to infer a relationship between objects.

The role of the Relationship Explorer was also distinguished: Overview enables discovery; Impact shows recorded dependencies; Technical Detail follows associations between Attributes, fields, Repositories, and Systems. An absence of a relationship must be explained as such, not filled in with an assumption.

## 2026-10-19 — Explanation of roles, scope, and modules strengthened

The documentation separates tenant role, capability, and scope. Roles do not replace the scope of a Domain, Subdomain, or Repository. The distinction between platform administration and operations within a company is also maintained.

The effect of configurable modules was added: a disabled module is no longer operable and its operations are rejected, but its data is not automatically deleted. Dependencies must be checked before planning a path that includes the Technical Dictionary, Quality Rules, Products, Contracts, or Relationship Explorer.

## 2026-10-19 — Quality and metadata limits documented

A Quality Rule does not generate SQL merely by existing. To do so, it needs a valid association with a physical field and a configured dialect. The documentation does not present SQL generation as automatic execution.

For metadata, it was recorded that configuration can be manual, daily, weekly, or monthly and that snapshots are versioned. The existence of these options does not allow an effective schedule, an available scan, or production jobs enabled for a specific company to be assumed.

## 2026-10-19 — Avoided creating catalogs not defined by the model

Risks and Controls are not described as independent modules or inventories. Controls are represented through existing objects, such as rules, policies or procedures, workflows, tasks, approvals, contracts, classifications, or certifications. States are limited to the context that is documented: for a company, only `provisioning`, `active`, `suspended`, `disabled`, and `deprovisioned`.

## Consolidated references

- [Object and relationship model](/en/explicaciones/modelo-de-objetos-y-relaciones/)
- [How to read the relationship map](/en/guias/como-leer-mapa-de-relaciones/)
- [Roles, capabilities, and scope](/en/referencia/roles-capacidades-y-alcance/)
- [Modules and dependencies](/en/referencia/modulos-y-dependencias/)