Cross-reference. The full Discussions rules live in the foundation triad.
The UniSaaS.UniCORE Discussions tab follows the same rules as the foundation triad's Discussions spaces. Rather than restate the full text here, this file points to the canonical sources.
UniVERSE/DISCUSSIONS.md(mirror: GitHub) — the canonical home of the rules.TrueAI/DISCUSSIONS.md(mirror: GitHub)UniCORE-AI/DISCUSSIONS.md(mirror: GitHub)
The three are byte-identical for the structural rules. The UniCORE-name extension is at UniCORE/DISCUSSIONS.md (mirror: GitHub).
The UniSaaS.UniCORE Discussions space inherits the foundation rules and adds the natural scope of the SaaS-deployment-shape name surface:
- Naming and classification questions about the open list of
UniSaaS.UniCORE.<Industry>classifications (the SaaS-deployment-shape equivalent ofUniCORE.<Industry>). - Deployment-shape questions about the relationship between
UniCORE.<Industry>(on-prem deployment shape) andUniSaaS.UniCORE.<Industry>(SaaS deployment shape) for the same governed substrate. - Cross-references to industry-classified sibling repositories (
UniSaaS.UniCORE.Law,UniSaaS.UniCORE.Healthcare, etc.) once those are created (per the certification-trigger lock; seeROADMAP.md). - Practical questions about how the UniSaaS.UniCORE name relates to specific Vertical Solutions delivered as a SaaS.
STATEMENT-ON-CLAIMS.md(this repository) — applies to participation here.BRAND-AND-TRADEMARK-USE-POLICY.md(this repository, cross-referencing the canonical version in the triad) — applies to participation here.- The badge-denial-on-military-uses rule (§4.5 of the brand/trademark policy; mirrored declaratively in
STATEMENT-ON-CLAIMS.md) applies fully.
- Public discussion: GitHub Discussions (when enabled)
- Private contact / connection request: LinkedIn
Author: Bryan Fred, Unitek Systems Limited, Bedford, United Kingdom. Public. Given, not sold. Irrevocable.