> For the complete documentation index, see [llms.txt](https://webuildssoftwaresolutions.gitbook.io/webuildssoftwaresolutions-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://webuildssoftwaresolutions.gitbook.io/webuildssoftwaresolutions-docs/documentation-disclosure-policy.md).

# Documentation Disclosure Policy

This policy defines what may be published through YARP.dev and the public GitBook sites.

## Public

Appropriate for unrestricted disclosure and search-engine indexing:

* product vision and supported use cases;
* high-level architecture and technology choices;
* public user journeys and module overviews;
* selected UI screenshots and public screen descriptions;
* API principles and integration concepts;
* developer guides that do not reveal sensitive implementation detail;
* public regulatory references and explanatory material;
* public security and privacy posture at a non-exploitable level.

## Customer / Partner

Shared only with approved customers, partners, auditors or enterprise evaluators:

* onboarding and implementation-readiness material;
* operational responsibilities;
* customer-facing security and privacy detail;
* integration expectations;
* assurance, recovery and support processes;
* contract- or NDA-scoped technical information.

## Internal

Keep out of public sites:

* detailed product strategy and unpublished roadmap decisions;
* implementation-level threat models and security controls;
* exact authorization, tenant-isolation and abuse-control internals;
* proprietary rule-engine and decision algorithms;
* internal AI prompts, orchestration and routing logic;
* exact infrastructure topology where disclosure adds risk;
* cost models and provider-selection logic;
* detailed delivery plans, architecture debt and internal backlog material;
* partner negotiations and commercial decision notes.

## Restricted

Do not publish through GitBook or YARP.dev:

* passwords, API keys, tokens and private keys;
* production database credentials;
* signing secrets;
* customer PII or private financial records;
* raw secret-bearing logs;
* sensitive incident credentials;
* any material that grants access merely by knowing it.

## Important rule

A hidden navigation item is not a security boundary. Sensitive content belongs in a private or authenticated site, or outside GitBook entirely when appropriate.

When a page mixes public and non-public material, classify it according to the most sensitive information on the page or split it into separate public and internal pages.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://webuildssoftwaresolutions.gitbook.io/webuildssoftwaresolutions-docs/documentation-disclosure-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.