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

# Authoring

This section gathers the **authoring guidelines** — the conventions, structure, and pitfalls to keep in mind when you create the content that drives CISO Assistant: frameworks, risk matrices, journey presets, and Excel-driven library content.

Authoring is a separate discipline from running the platform. Once content has been authored, it's loaded through the [Libraries](/ciso-assistant/configuration/libraries.md) section and behaves the same as any built-in content — versioned, upgradable, exportable. The pages here focus on *writing the content*, not on loading it.

For frameworks, matrices, and presets, the **recommended path is the in-app visual editor**. These are now unified in a single [Library builder](/ciso-assistant/configuration/authoring/library-builder.md) under the `/experimental/` namespace: you author a whole library as a **draft document** — never touching live objects — then publish it through the standard loader, or export/import it as YAML. Draft/publish lifecycle, live preview, real-time validation, and multi-language support all apply. Excel-driven authoring remains the right channel for library publishing across instances.

## What's in this section

* [Library builder](/ciso-assistant/configuration/authoring/library-builder.md) — the unified entry point for authoring library content in the app: author a full library (or a single framework/matrix in simple mode), build requirement trees, matrices, threats, reference controls, and journey presets, adopt or clone existing content, import/export YAML, and publish through the standard loader.
* [Excel-driven authoring](/ciso-assistant/configuration/authoring/excel.md) — the recommended workflow for authoring frameworks, matrices, and other library content from Excel before conversion to YAML.

## When to read this section

* You're building your own framework (industry-specific, internal policy, regulatory adaptation) and want to do it right the first time.
* You're **forking an existing framework** as a baseline — copying a built-in or community library, then tuning it to your context (renaming the URN, pruning, adding in-house requirements) rather than starting from a blank page.
* You're modelling a custom risk matrix that needs to match your enterprise's existing risk taxonomy.
* You're standardising a journey preset for a recurring assessment pattern (yearly ISO audit, supplier onboarding, new project intake).
* You want to understand the editorial rules behind the platform's built-in content before contributing or forking it.

## Related

* [Libraries](/ciso-assistant/configuration/libraries.md) — how to load, upgrade, and clean up authored content.
* [Designing your own libraries](/ciso-assistant/configuration/libraries/custom-libraries.md) — the full Excel-to-YAML workflow that backs framework and matrix authoring.
* [Contributing → Frameworks and libraries](/ciso-assistant/contributing/framework.md) — how to upstream authored content to the community library.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://intuitem.gitbook.io/ciso-assistant/configuration/authoring.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.