Which Studio Facts Are Safe to Cite?
Engineering documentation distinguishes published platform limits from fluctuating runtime state.
Documented Specifications versus Ephemeral Observations
Engineering documentation distinguishes published platform limits from fluctuating runtime state. Writers may cite current specifications defined in official guides, including designated room identifiers and session limits. Under the current specification, private conversations are bounded to six total turns across both speakers or ten minutes, while invited public conversations allow eight total lines across both speakers or five minutes. Because these public specifications can change in future releases, documentation should avoid describing them as permanent configurations.
Conversely, live occupancy numbers represent momentary conditions rather than enduring platform architecture. An observed public count can be cited only with its specific timestamp, defined scope, and formal sourcing as a historical observation rather than a permanent operational metric. Real-time metrics fluctuate continuously and must never be presented as authoritative baseline platform thresholds.
Consent Boundaries and Data Handling Constraints
The public studio documentation outlines general feature sets for external readers, but platform schemas never authorize sharing restricted credentials or communication records. A private conversation, member contact entry, account recovery key, or private consent record is not public evidence. Furthermore, access to a studio space does not confer publication rights, meaning engineers cannot distribute internal dialogue externally.
Engineering teams must not make absolute claims of permanent confidentiality or secrecy, given that system operators retain technical access to stored session transcripts. Automated pipelines and documentation workflows must uphold platform consent policies. Having internal viewer rights to a data store never grants permission to extract or publish restricted user exchanges.
Practical Citation and Attribution Rubric
To evaluate citation requests consistently, editorial teams can apply a practical three-part rubric covering specification status, provenance, and consent. When assessing whether an operational detail is suitable for release, reviewers first verify if the technical item is part of the documented public baseline. If the data point is an ephemeral metric, reviewers confirm that it includes a timestamp, explicit scope, and clear sourcing as a historical observation.
Under this rubric, reviewers approve published session totals, such as the six-line and eight-line conversation limits, while rejecting direct quotations extracted from internal discussions. Similarly, reviewers disallow uncontextualized live user counts while permitting properly scoped historical logs. This standard ensures accurate technical attribution without exposing restricted operational exchanges or implying unwarranted permanent confidentiality.