Praxis Java Domain Governance Field Access
Treat governance as canonical domain semantics with backend enforcement. Metadata
explains and materializes safe behavior; it never makes Angular visibility,
x-ui.fieldAccess, masking hints, or capabilities a substitute for authorization.
Classify The Field In Its Business Context
Inspect product documentation, DTO operation role, entity/view source, existing
annotations, authorization, export/stats/filter/lookup behavior, AI consumers,
logs, and tests. Record purpose, data category, sensitivity, source of truth,
who may read/edit/export it, masking expectation, AI use, retention evidence,
and analytic eligibility. Do not infer legal basis or retention when evidence is absent.
Classify a proposed governance field or policy as ja-suportado-so-ux,
ja-suportado-mal-nomeado-ou-mal-materializado, suportado-parcialmente, or
lacuna-real-de-contrato. Reuse @DomainGovernance, AiUsagePolicy, filtered
schema, domain catalog, field access, export/stats and option-source contracts
before proposing a parallel host-specific metadata model.
Author The Governed Contract
- Use
@Schema for verified business meaning and @DomainGovernance for
classification, purpose, visibility, governance evidence, and AI implications.
Do not use a generic label or database column as domain explanation.
- Set AI usage deliberately. Secrets, credentials, raw private notes, health,
payroll, disciplinary, security, and high-risk personal data are excluded or
masked unless a governed use case proves otherwise. Do not expose them to RAG,
reasoning, training, summaries, or automated action by default.
- Publish
x-ui.fieldAccess only as a materialization of a backend-governed
policy. Enforce read/edit/filter/export/action access on the server and test a
denied caller. Capabilities are not implicit field authorities.
- Apply least exposure across response DTOs, create/update DTOs, filters,
option labels/search, analytics, exports, logs, errors, and generated docs.
A field may be allowed in one surface and excluded in another only with an
explicit purpose and consumer proof.
- Treat audit/provenance and technical legacy fields deliberately: normally
read-only, grouped, hidden from write forms, and excluded from AI/export/stats
unless the business need is verified. Never publish tokens, session, SQL,
ROWID, package, or provider internals.
- Keep masking/redaction semantics consistent with raw access. A mask is not
authorization; do not return raw data in hidden payloads, exports, filters,
option source search, analytics, or error text after a UI mask is declared.
Read field-governance-matrix.md when
deciding exposure across operations and consumers.
Prove Enforcement And Materialization
Prove one allowed and one denied context for sensitive fields. Verify emitted
schema/domain governance/field-access metadata, backend read/write/filter/export
enforcement, masking behavior, AI policy, logs/errors sanitization, and direct
Angular materialization. When the field is excluded from stats/export/options,
prove that those paths reject or omit it without silently widening data exposure.
Use focused DTO/schema/governance tests plus affected resource, option-source,
stats/export, and quickstart HTTP evidence. Run Angular schema-normalizer or
field-access consumer specs when public metadata changes. Review docs/corpus only
when they publish the changed governance claim.
Companion Skills
praxis-dto-annotations: semantic descriptions, UI metadata, and DTO roles.
praxis-java-stats-export-authoring: analytics/export field eligibility.
praxis-java-option-source-provider-authoring: lookup search/display exposure.
praxis-java-error-response-contracts: sanitized errors and diagnostics.
praxis-java-contract-conformance: final cross-consumer evidence.
Close with the field matrix, policy evidence, allowed/denied proof, consumer
coverage, and any unverified governance decision. A field is governed only when
the server and all published projections agree on its permitted use.
1---2name: praxis-java-domain-governance-field-access3description: "Use when implementing, auditing, or migrating Praxis Java domain governance and field access: @DomainGovernance, AiUsagePolicy, x-ui.fieldAccess, personal/sensitive/financial/security data, masking, export and analytics eligibility, filters and option sources, audit/provenance fields, semantic domain catalog, and backend enforcement with Angular materialization."4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-java-domain-governance-field-access6---78# Praxis Java Domain Governance Field Access910Treat governance as canonical domain semantics with backend enforcement. Metadata11explains and materializes safe behavior; it never makes Angular visibility,12`x-ui.fieldAccess`, masking hints, or capabilities a substitute for authorization.1314## Classify The Field In Its Business Context1516Inspect product documentation, DTO operation role, entity/view source, existing17annotations, authorization, export/stats/filter/lookup behavior, AI consumers,18logs, and tests. Record purpose, data category, sensitivity, source of truth,19who may read/edit/export it, masking expectation, AI use, retention evidence,20and analytic eligibility. Do not infer legal basis or retention when evidence is absent.2122Classify a proposed governance field or policy as `ja-suportado-so-ux`,23`ja-suportado-mal-nomeado-ou-mal-materializado`, `suportado-parcialmente`, or24`lacuna-real-de-contrato`. Reuse `@DomainGovernance`, `AiUsagePolicy`, filtered25schema, domain catalog, field access, export/stats and option-source contracts26before proposing a parallel host-specific metadata model.2728## Author The Governed Contract29301. Use `@Schema` for verified business meaning and `@DomainGovernance` for31 classification, purpose, visibility, governance evidence, and AI implications.32 Do not use a generic label or database column as domain explanation.332. Set AI usage deliberately. Secrets, credentials, raw private notes, health,34 payroll, disciplinary, security, and high-risk personal data are excluded or35 masked unless a governed use case proves otherwise. Do not expose them to RAG,36 reasoning, training, summaries, or automated action by default.373. Publish `x-ui.fieldAccess` only as a materialization of a backend-governed38 policy. Enforce read/edit/filter/export/action access on the server and test a39 denied caller. Capabilities are not implicit field authorities.404. Apply least exposure across response DTOs, create/update DTOs, filters,41 option labels/search, analytics, exports, logs, errors, and generated docs.42 A field may be allowed in one surface and excluded in another only with an43 explicit purpose and consumer proof.445. Treat audit/provenance and technical legacy fields deliberately: normally45 read-only, grouped, hidden from write forms, and excluded from AI/export/stats46 unless the business need is verified. Never publish tokens, session, SQL,47 ROWID, package, or provider internals.486. Keep masking/redaction semantics consistent with raw access. A mask is not49 authorization; do not return raw data in hidden payloads, exports, filters,50 option source search, analytics, or error text after a UI mask is declared.5152Read [field-governance-matrix.md](references/field-governance-matrix.md) when53deciding exposure across operations and consumers.5455## Prove Enforcement And Materialization5657Prove one allowed and one denied context for sensitive fields. Verify emitted58schema/domain governance/field-access metadata, backend read/write/filter/export59enforcement, masking behavior, AI policy, logs/errors sanitization, and direct60Angular materialization. When the field is excluded from stats/export/options,61prove that those paths reject or omit it without silently widening data exposure.6263Use focused DTO/schema/governance tests plus affected resource, option-source,64stats/export, and quickstart HTTP evidence. Run Angular schema-normalizer or65field-access consumer specs when public metadata changes. Review docs/corpus only66when they publish the changed governance claim.6768## Companion Skills6970- `praxis-dto-annotations`: semantic descriptions, UI metadata, and DTO roles.71- `praxis-java-stats-export-authoring`: analytics/export field eligibility.72- `praxis-java-option-source-provider-authoring`: lookup search/display exposure.73- `praxis-java-error-response-contracts`: sanitized errors and diagnostics.74- `praxis-java-contract-conformance`: final cross-consumer evidence.7576Close with the field matrix, policy evidence, allowed/denied proof, consumer77coverage, and any unverified governance decision. A field is governed only when78the server and all published projections agree on its permitted use.