DGS architecture is not publicly revealed. Public documentation explains what DGS is, how outputs should be read, and where trust, review, and access boundaries sit.
Internal architecture, routing logic, execution mechanics, and reverse-engineerable system detail remain protected. Public use of DGS does not create a right to those materials.
A serious system can publish a clear identity and output standard without publishing its private architecture. That boundary protects the system while keeping the public surface intelligible.