The short version#
An output is something Sidekick or another governed agent produced: a file, draft, bundle, report, patch, replay package, or deployment record.
An artifact is the governed record behind that output. It tells LumenFlow what was produced, which agent or participant produced it, which job or handoff it belongs to, where it lives, who can access it, and which evidence, replay, or approvals are attached.
A destination is the place an output should land: managed artifacts inside LumenFlow, a code host, a document store, an artifact store, a deployment provider, a connected runtime, or a manual export path.
Managed links, hosted app pages, and connected deployments#
Saving something and making it public are different actions, and LumenFlow keeps them clearly separate.
When a governed agent saves a generated file in managed artifacts, LumenFlow can give workspace members and authorized participants a view, download, preview, or export link. That link is workspace-scoped and governed by your workspace permissions.
It is not a public website, CDN, custom domain, or production deployment.
If you ask Sidekick, an external agent, or a fleet worker to "host this page," there are two honest paths, and LumenFlow always tells you which one applies before anything goes live:
- A hosted app page — a small, self-contained page (a demo, prototype, or utility) can be published directly on LumenFlow's own managed hosting as a sandboxed, revocable public page. Nothing goes live until you explicitly confirm; once published, anyone with the link can view it until it's taken down. See Hosted app pages.
- A connected deployment destination — Sidekick can deploy a built site to a destination you've connected and approved, such as GitHub Pages or your own Vercel project, rather than hosting it itself. This is for a site that ships as static files; a full app that needs its own backend, database, or server-side code is beyond what Sidekick deploys for you.
Either way, the agent only ever tells you a public link exists once the publish or deployment step has actually returned one — never a guess, and never in advance.
How Sidekick fits the platform#
Sidekick is one surface of LumenFlow, a governed agent runtime and control plane. The same policy, approvals, budgets and evidence apply to every surface. Artifacts are the handoff objects. They keep proof and routing straight, while your own tools remain the source of truth for code, documents and deployments.
What people can build#
LumenFlow-governed agents can help you build:
- software changes with tests and pull requests
- generated documents, summaries, reports, and export bundles
- small static files or HTML pages as workspace-scoped outputs, or published directly as a hosted app page
- replay and evidence packages for audit or review
- workflow definitions and connected-app actions
- deployable code or assets that are ready to hand to a connected destination
A simple, self-contained page can be published directly as a hosted app page once you confirm. They cannot turn an internal output into a full production website with a backend by themselves — that always routes to a connected deployment destination, with your explicit confirmation and a real URL returned by that step.
Common terms#
| Term you may see | Plain label | What it means |
|---|---|---|
| Artifact | Output, generated file, export | Something Sidekick or another governed agent produced and saved with a traceable record. |
| Job | Work, task | A tracked piece of work one or more governed agents are carrying out for you or your team. |
| Runtime | Worker, execution environment | The place where governed work runs, whether hosted by LumenFlow or connected from your environment. |
| Pack | Capability, workflow type | A bundle of rules and tools for a kind of work, such as software delivery. |
| Destination | Connected tool, publish target | The app or service where an output should land. |
| Evidence | Proof, activity record | The record of what happened, who approved it, and which rules applied. |
| WU | Task, change | A scoped software-delivery task with files, gates, and evidence. |
On desktop, these terms should have helper text or info tooltips. On mobile, they should use tap-to-open explanations, inline help, or bottom sheets rather than hover-only tooltips.
Can LumenFlow host what I build?#
Yes, within a defined scope. For a simple page — a demo, prototype, or small utility — LumenFlow can publish it directly on its own managed hosting as a sandboxed, revocable page once you confirm. LumenFlow is not the canonical host for a full production website: for a full app that needs a backend, a database, or server-side code, it routes the code to the deployment destination you've connected and approved instead of hosting it itself.
For code and deployment, LumenFlow works with the systems you choose. Your code host remains the source of truth for source code. Your connected deployment destination remains the source of truth for a full production deployment.