The Three Main Parts of Halo Lumin

Halo Lumin is built around a simple idea: make useful information easy to share, easy to read, and easy to reuse. A Halo can be a file, a piece of text, a Markdown page, or a reusable prompt. The ecosystem has three main parts that work together: Halo Lumin, Halo Forge, and Halo MCP / Agent Access.

1. Halo Lumin

What it does

Halo Lumin turns a file or pasted text into a clean, shareable web page. Instead of sending someone a download prompt, a cloud-drive permission screen, or a messy attachment, you create a Halo and share the link.

A Halo can support common content types such as PDFs, images, JSON, plain text, and Markdown. Viewers can open the shared page without creating an account, while signed-in creators can manage their own Halos, choose expiration options, update content, and use human-readable public URLs when available.

Who it helps

Halo Lumin is for people who need to share one useful thing clearly and quickly:

• Freelancers sharing proposals, invoices, or one-pagers
• Teachers sharing reading materials or class resources
• Realtors sharing property sheets or market updates
• Consultants sharing recommendations or client-ready summaries
• Anyone who wants a simple public reading link instead of a file handoff

Why it matters

The important shift is that the share link opens as readable content first. Halo Lumin is not trying to be a full cloud drive or a document editor. It focuses on the moment when someone says, “Here is the thing. Please read it.”

That focus makes the experience cleaner for both sides: creators can publish quickly, and recipients can review the content without logging in, installing an app, or hunting for the right download button.

2. Halo Forge

What it does

Halo Forge is the prompt-building part of Halo Lumin. It helps signed-in users create clearer, more reusable AI prompts through a guided flow.

Instead of starting from a blank box, users choose a starting point such as Learn, Create, or Review, describe what they need, and let Halo Forge suggest a practical setup. The user can adjust the setup, build a structured Markdown prompt, optionally strengthen it with AI, then copy it or save it as a Halo.

How it helps users build better prompts

Halo Forge helps users slow down just enough to make the prompt useful. It asks for intent, output direction, and style choices before producing the final prompt. That keeps the prompt focused on the task, the audience, and the expected result.

For example, a user might want to learn a concept, create a plan, review a document, or analyze results. Halo Forge gives that work a shape before the prompt is sent to an AI system.

How it connects to Halos

A prompt built in Halo Forge can become a normal text or Markdown Halo. That means useful prompts can be saved, shared, revisited, and reused like other Halo content.

This turns prompt-building from a one-time chat habit into a lightweight publishing and reuse workflow: build the prompt, improve it, save it, and share it when helpful.

3. Halo MCP / Agent Access

What it does

Halo MCP / Agent Access lets authorized AI agents work with a user’s own Halos through a narrow, scoped tool surface. At a high level, it gives agents a controlled way to search owned Halos, read safe text-backed Halo content, and, when explicitly allowed, create new text or Markdown Halos.

MCP support makes this available through a standard agent-facing protocol, while Agent Access keys let users decide what a specific agent is allowed to do.

Read-only vs. create-enabled access

Agent Access is scope-based. A read-only key can list or search owned Halos and fetch safe metadata or stored text content for Halos the key owner controls. It does not grant broad account access, file download access, update access, delete access, or cross-user access.

A create-enabled key can create new owned text or Markdown Halos when that permission is explicitly granted. Creation is intentionally narrow: it is for text and Markdown publishing, not arbitrary file uploads or unrestricted account actions.

This separation matters because different agents need different levels of trust. Some should only help find and read existing material. Others may be allowed to publish a new Markdown Halo on the user’s behalf.

Why scopes and audit events matter

Scopes make Agent Access understandable and limited. A user can grant only the access needed for the job, such as reading owned Halos, creating text/Markdown Halos, or both.

Audit events add accountability. Successful agent actions are recorded with safe metadata, such as which tool was used and whether the action succeeded, without storing raw keys, raw prompts, returned content, private file bytes, or sensitive access tokens. That gives Halo Lumin a foundation for responsible agent workflows while keeping the tool surface intentionally small.

How the three parts work together

The three parts are designed to support one another:

• Halo Lumin is the publishing and sharing layer. It turns content into clean web pages people can open without friction.
• Halo Forge is the creation layer for reusable AI prompts. It helps people make better instructions and save them as Halos.
• Halo MCP / Agent Access is the agent layer. It lets trusted tools work with a user’s Halos through limited, explicit permissions.

Together, they form a simple loop: create or collect useful content, turn it into a Halo, reuse it when needed, and let authorized agents help only within the boundaries the user chooses.

Closing thought

Halo Lumin is not just a place to put files. It is a way to make useful information easier to share, easier to understand, and easier to reuse with both people and AI tools.