# liquidware-ninja: Liquidware knowledge base (liquidware-ninja)

> The Liquidware second brain: a living knowledge base of findings, architecture, API notes,
> SpotCheck thresholds, gotchas and decisions for running Liquidware products (Stratusphere UX,
> ProfileUnity, FlexApp and CommandCTRL) across virtual and physical desktops, including Azure
> Virtual Desktop and FSLogix. Shared by a family of sibling knowledge bases that use the 2ndbrain
> format.

The knowledge base is in docs/knowledge/. Every page starts with YAML front matter (title, summary,
topic, status, last_reviewed) validated against docs/knowledge/schema/. Pages with status `plan`
describe intended work, not facts, and claims marked *unverified* are not yet confirmed. To
contribute, open a KB feedback or known-error issue; changes land only through reviewed pull requests.

## Knowledge base

- [Knowledge base](docs/knowledge/README.md): What this knowledge base is, how it's organised, and how to add to it safely (status: partial)
- [Prior art and community projects](docs/knowledge/liquidware/community-projects.md): Public code and tools around Stratusphere, with their licenses and what this project may reuse (status: verified)
- [Liquidware products and where they're documented](docs/knowledge/liquidware/products.md): Which Liquidware products this KB covers, how our repos divide the work, and where Liquidware publishes docs, support articles and news (status: verified)
- [Asks for Liquidware](docs/knowledge/liquidware/upstream.md): Gaps found while automating Stratusphere in Azure, with the evidence, to raise with Liquidware (status: partial)
- [Stratusphere API](docs/knowledge/stratusphere/api.md): The Hub's read-only data API: request shape, inspectors, basis, parameters, authentication, output formats and ecosystem prior art (status: partial)
- [Stratusphere UX appliances in Azure](docs/knowledge/stratusphere/appliances.md): Hub, Database and Collector roles: when each is needed, sizes, addresses, credentials and what hasn't been confirmed on a real run (status: unverified)
- [Connector ID Key](docs/knowledge/stratusphere/connector-id-key.md): The Stratusphere agent on each desktop: installer switches, callbacks to the Hub, where its services and settings live, and images created later (status: partial)
- [First-time Hub setup](docs/knowledge/stratusphere/hub-setup.md): What has to be set in the Hub console after deployment (license, API user, API allow list) and what might move to the API (status: unverified)
- [SpotCheck thresholds, canonical dataset and sizing](docs/knowledge/stratusphere/spotcheck-and-sizing.md): How Stratusphere UX data turns into SpotCheck findings, sizing tiers and before/after migration baselines (status: verified)
- [ProfileUnity architecture, Portability and configuration promotion](docs/knowledge/profileunity/architecture-and-portability.md): How ProfileUnity manages user environments and Portability alongside profile containers, and how to promote configurations safely (status: partial)
- [FlexApp packaging, VHDX/CimFS and App Attach delivery](docs/knowledge/flexapp/packaging-and-delivery.md): How FlexApp packages applications into elastic layers and delivers them natively or through AVD App Attach (status: partial)
- [CommandCTRL overview and real-time support](docs/knowledge/commandctrl/overview.md): Where Liquidware CommandCTRL fits for real-time helpdesk diagnostics and remediation next to Stratusphere UX (status: partial)
- [Liquidware across desktop platforms](docs/knowledge/platforms/multi-platform-matrix.md): How Stratusphere UX, ProfileUnity, FlexApp and CommandCTRL behave across AVD, Windows 365, Citrix, Horizon, RDS and physical PCs (status: verified)
- [How Liquidware products fit with Azure Virtual Desktop and FSLogix](docs/knowledge/avd/fit-with-avd-and-fslogix.md): Which job each Liquidware product does next to AVD's own features and FSLogix: profiles, app delivery, support and assessment (status: partial)
- [Lab costs and teardown](docs/knowledge/azure/lab-costs.md): What keeps billing while a Stratusphere lab is stopped, and why a lab run ends torn down (status: partial)
- [Stratusphere in Azure Marketplace](docs/knowledge/azure/marketplace.md): Liquidware's Marketplace offer: finding the plan for a region, the plan block a VM needs, and accepting terms per subscription (status: partial)
- [Networking for Stratusphere in Azure](docs/knowledge/azure/networking.md): The ports the appliances and Connector ID Keys need, egress without default outbound access, peering, and how routes affect callbacks (status: unverified)
- [Deployment gotchas](docs/knowledge/deployment/gotchas.md): What trips up a Liquidware deployment in Azure, across products, with a link to where each is explained (status: partial)
- [Known errors](docs/knowledge/troubleshooting/README.md): Errors hit in this project: symptom, cause, fix and source (status: partial)
- [Roadmap](docs/knowledge/roadmap/README.md): What this knowledge base plans to cover next (status: plan)
- [Keeping the knowledge base current](docs/knowledge/curation.md): How the KB stays current: the weekly digest, the prior-art check, the feedback loop, the freshness check and family alignment (status: verified)
- [Experts we follow](docs/knowledge/experts.md): How we choose which people on this KB's topics the KB follows: the method, the scores and the list (status: verified)

## Structured data

- [Known errors](docs/knowledge/troubleshooting/known-errors.yaml): symptom, cause, fix and source for errors hit with Liquidware products
- [Field reports](docs/knowledge/field-reports.yaml): what worked or broke when someone followed the KB
- [Experts study](docs/knowledge/experts.yaml): people the KB follows, with scores, evidence and the feeds watched
- [Family](docs/knowledge/family.yaml): the sibling knowledge bases and the format version each follows
- [Schemas](docs/knowledge/schema/page.schema.json): JSON Schemas for page front matter and the YAML files above

## Decisions

- [0001. Adopt the 2ndbrain knowledge base format, version 1](docs/knowledge/decisions/0001-adopt-the-2ndbrain-format.md): accepted
- [0002. MIT for the repo; the knowledge base tooling keeps Apache-2.0](docs/knowledge/decisions/0002-mit-license-apache-kb-tooling.md): accepted
- [0003. This repo deploys the Liquidware platform; assessment and design live elsewhere](docs/knowledge/decisions/0003-deploy-here-assess-and-design-elsewhere.md): proposed
- [0004. Deploy appliances from Azure Marketplace; no Liquidware binaries or license material in the repo](docs/knowledge/decisions/0004-marketplace-appliances-no-vendor-binaries.md): proposed
- [0005. Bicep with pinned Azure Verified Modules, following avd-landing-zone](docs/knowledge/decisions/0005-bicep-with-azure-verified-modules.md): proposed
- [0006. Generated credentials go to Key Vault, and reruns reuse them](docs/knowledge/decisions/0006-credentials-in-key-vault.md): proposed
- [0007. Real runs are the source of truth; every lesson adds a guard](docs/knowledge/decisions/0007-real-runs-are-the-source-of-truth.md): proposed
- [0008. Everything runs from Azure Cloud Shell](docs/knowledge/decisions/0008-cloud-shell-baseline.md): proposed
- [0009. Unlicensed code is reference only](docs/knowledge/decisions/0009-unlicensed-code-reference-only.md): proposed
- [0010. Prefer Azure-native, GitHub, HashiCorp and open-source tooling](docs/knowledge/decisions/0010-prefer-azure-github-hashicorp-oss.md): proposed
- [0011. Family format: a guard field on known errors](docs/knowledge/decisions/0011-family-format-guard-on-known-errors.md): proposed
- [0012. Family format: the upstream asks file's path set in kb.toml](docs/knowledge/decisions/0012-family-format-upstream-path-in-kb-toml.md): proposed
- [0013. Follow the family's model-selection convention](docs/knowledge/decisions/0013-family-model-selection-convention.md): proposed
- [0014. Pilot the family's enforced knowledge capture, in warn mode](docs/knowledge/decisions/0014-family-format-enforced-kb-capture-pilot.md): accepted
- [0015. Take handoffs from other Claude projects as `handoff` issues](docs/knowledge/decisions/0015-family-format-handoff-issues.md): accepted
- [0016. Follow the family's GitHub work conventions, with low-risk PRs merging themselves](docs/knowledge/decisions/0016-family-format-github-work-conventions.md): proposed
- [0017. Consolidate the Liquidware second brain and toolkit in liquidware-ninja](docs/knowledge/decisions/0017-consolidate-liquidware-second-brain-in-liquidware-ninja.md): accepted
- [0018. Publish the liquidware-ninja site on Cloudflare Workers under liquidware-ninja.prignano.ai](docs/knowledge/decisions/0018-publish-site-on-cloudflare.md): accepted

## Related knowledge bases

- [2ndbrain](https://github.com/nickprignano/2ndbrain/tree/main/docs/knowledge): The template that owns the family knowledge base format. Source of truth for: the family knowledge base format; its scripts and schemas
- [avd-ops](https://github.com/avd-ops/avd-ops/tree/main/docs/knowledge): The front door for the AVD repos: avd-ops.dev, onboarding and user docs. Source of truth for: onboarding and user-facing docs for the AVD repos; the avd-ops.dev site and design system
- [Nerdio HCL kit](https://github.com/nickprignano/nerdio-hcl/tree/main/docs/knowledge): Nerdio Manager on Azure Virtual Desktop, deployed with Terraform and Packer. Source of truth for: Nerdio Manager; the nerdio/nme provider; this kit's Terraform and Packer
- [AVD](https://github.com/avd-ops/avd-second-brain/tree/main/docs/knowledge): Azure Virtual Desktop itself. Source of truth for: Azure Virtual Desktop platform; FSLogix; session host images in general
- Private layer (repo not linked yet): The maintainer's private wisdom layer. It reads the family through this hub and sends directives here as pull requests; its contents stay private. Source of truth for: Directives to the family; through docs/knowledge/directives.yaml

## Optional

- [Curator sources](docs/knowledge/sources.toml): the feeds and repos the weekly digest watches