# FusappWork developer documentation > English documentation for Work customers and integrators. Work SDK is planned and not published. Do not invent package installs, endpoints or options. Status labels: available (documented content or source contract; no live-service promise), Train 2, Train 3, planned. ## Pages - [Page not found](https://docs.fusapp.work/404.md): available. Return to the FusappWork documentation. - [AI coding prompts](https://docs.fusapp.work/ai/prompts.md): available. Copy a short, grounded preparation prompt into your AI coding tool. - [Integration concepts](https://docs.fusapp.work/concepts.md): available. A plain-English introduction to products, workspaces and SDK integration. - [FusappWork developer documentation](https://docs.fusapp.work/index.md): available. Understand integration concepts and prepare for the planned Work SDK. - [Work SDK](https://docs.fusapp.work/sdk/work.md): planned. The planned SDK for applications integrating with FusappWork. - [Documentation status](https://docs.fusapp.work/status.md): available. How to interpret availability and planned capabilities. ## Full reference - [llms-full.txt](https://docs.fusapp.work/llms-full.txt): All public pages, with status labels. --- Source: https://docs.fusapp.work/404.md # Page not found Status: available Audience: public This documentation page could not be found. [Return to the overview](/), explore [integration concepts](/concepts/), or review the [planned Work SDK](/sdk/work/). --- Source: https://docs.fusapp.work/ai/prompts.md # AI coding prompts Status: available Audience: public Paste the prompt below into your AI coding tool. Supply your application requirements, without credentials or personal data. ## Prepare a Work SDK integration ```text Read https://docs.fusapp.work/llms.txt and the Work SDK page. The Work SDK is planned and is not published yet. Help me prepare an integration brief for my application: describe the business task, server boundary, workspace context, runtime requirements and questions that need a released contract. Do not invent installation commands, endpoints, options or versions. Separate documented facts from requirements and unknowns. ``` Use the documentation at [docs.fusapp.work](https://docs.fusapp.work) as your reference. Give your coding tool the Markdown links or `llms-full.txt` to include the documented scope and status labels. ## Choose the right format - [llms.txt](/llms.txt): a short index of this documentation. - [llms-full.txt](/llms-full.txt): the full public reference with page statuses. - [This page as Markdown](/ai/prompts.md): a direct text version. An **available** prompt helps with preparation. It does not make a planned SDK available. --- Source: https://docs.fusapp.work/concepts.md # Integration concepts Status: available Audience: public FusappWork brings business operations into a workspace. This page introduces the vocabulary used in these docs. It describes concepts; it is not an API contract. ## Product, workspace and integration | Term | Meaning in these docs | | ----------- | ----------------------------------------------------------------------- | | Product | The application you are building or connecting. | | Workspace | The business context in which people work. | | SDK | A package intended to help application code communicate with a service. | | Integration | The connection between your application and FusappWork. | ## Plan the boundary Identify what your application owns and what it needs from FusappWork. Write down the user task, the workspace context, and the outcome you expect. Keep credentials out of browser code, documentation and AI prompts. The [Work SDK](/sdk/work/) is planned. These docs do not yet define installation commands, callable endpoints, configuration options or authentication setup for that package. ## Prepare without guessing You can describe your application architecture and the operations you need. Separate those requirements from released capabilities. Use the [AI preparation prompt](/ai/prompts/) to produce a list of questions rather than speculative implementation code. --- Source: https://docs.fusapp.work/index.md # FusappWork developer documentation Status: available Audience: public ## Find your starting point - [Understand the concepts](/concepts/) — **available**. Learn how a product, workspace and integration fit together. Start here if you are new to FusappWork. - [Explore the Work SDK](/sdk/work/) — **planned**. Review the intended scope and the information you can prepare. The SDK is not published yet. ## Bring your AI coding tool Read these docs as [Markdown](/index.md), browse the [AI index](/llms.txt), or load the [full reference](/llms-full.txt). Use a [short preparation prompt](/ai/prompts/) to keep your coding tool grounded in the documented scope. ## Know what is ready Every page has a status. **available** means the information is ready to read; it does not promise a live API. **planned** means the integration is not released. Check [documentation status](/status/) before starting implementation. --- Source: https://docs.fusapp.work/sdk/work.md # Work SDK Status: planned Audience: public The Work SDK is planned for FusappWork customers and integrators. It is **not published yet**. There is no supported package installation or working quickstart to run from this page. ## Intended direction The planned .NET package name is `FusappWork.Sdk`. Public distribution is intended for a later release. Package versions, language support, callable APIs and configuration options will be documented when their release is verified. ## What you can prepare 1. Describe the application and the business task you want to connect. 2. Identify the server component that would own the integration. 3. List the information you need to read or write and the workspace context for each operation. 4. Record your target language and runtime as requirements. ## Release evidence required A released package, a verified installation command, an accepted API contract and a tested example are needed before this page can become an implementation guide. No release date is promised here. Use the [AI preparation prompt](/ai/prompts/) to organize your questions. --- Source: https://docs.fusapp.work/status.md # Documentation status Status: available Audience: public Status labels describe the scope of each page. They do not replace package release evidence or a service acceptance check. | Label | Meaning | | --------- | -------------------------------------------------------------------------------------------------------- | | available | The documented information is ready to read. Any implementation claim needs an explicit source contract. | | Train 2 | Reserved for capabilities assigned to the second delivery train; not a release promise. | | Train 3 | Reserved for capabilities assigned to the third delivery train; not a release promise. | | planned | Intended scope without a verified public release. | ## Current scope General integration concepts and AI preparation prompts are **available**. The **Work SDK is planned and not published**. Installation commands, endpoint reference and runnable examples will follow verified release evidence. FusappWork developer documentation is published at [docs.fusapp.work](https://docs.fusapp.work). Page status labels describe the documented capabilities and their release evidence.