Get started

Learn the boundary first, then run a real path. About 90 seconds to your first result.
How it stays safe Halcyon shares the status and a short summary so a reviewer can act. The controlled file stays protected. A reviewer approves before anything is shared outside. Candidate workspace, mock data only.

Start here

New to this? Take two minutes first.

A short listen and a short watch, in plain language. What Halcyon is, why a computer doing this work is the right call, and what you get in your first week. No background needed.

2-minute listen

The quick listen

About a minute and a half. The written version is below if you would rather read.

Read it instead

You have a file you care about, in five versions across three folders. Finding the right one by hand eats an afternoon. Halcyon finds it for you, shows what changed, and keeps the protected file protected. Then a person signs off, and that signed result is the point.

Why let a computer do it? It does the boring search so you do the judgment. It catches the mistakes people make when they rush. And it keeps what a leaving expert knows, written down as the work happens.

2-minute watch

The quick watch

About two minutes. Same story as the listen, with visuals.

What it covers

Six short beats: the messy-file problem, what Halcyon does, the three reasons a computer should do it, why it stays safe (think airport security, the screener reads the tag and a person opens the bag), what you get in week one, and the one rule.

Boring search, your judgment It reads names, dates, and statuses across every folder in seconds and never skips one. You make the call only a person can make.
Catches rushed mistakes A wrong version sent out, a number in the wrong field. It compares what should match and flags what does not, before it becomes a problem.
Keeps what an expert knows When someone retires, what they carried usually leaves with them. Halcyon writes down the proof behind each call, so the next person picks up where the last one left off.

About the engine: you will hear the word "model," the engine that reads text and finds patterns. Several companies make them, and Halcyon is not tied to one. If a better engine arrives next year, what you learned does not change. You learn Halcyon once.

Your first small wins

One click, one clear result

Start small. Each of these is a single task with a single answer. No setup, no dashboard to learn first.

Find Find the right version See which file is the latest across folders, with what changed called out. Open the evidence flow Compare See what changed Pull the readable fields from a file and read a plain list of what moved between versions. Open Documents Check Catch a problem early Run a quick check and see pass or hold, with the open items, before anything is committed. Open the simulator

New here

Find the right version. Read the proof. Make the call.

You do not need to be technical to get value in week one. Halcyon finds the right version of a file across folders and systems, shows what changed, and keeps controlled files protected. This page shows you what gets shared and what stays protected, then hands you a real path to run.

Open the proof map Build a path in Flow Open the result packet
Learn it fast The basics take about 90 seconds. Then you run a real path.
One deliverable Every path ends at the readiness packet. That reviewed packet is the point.
No controlled data Status and summary only. No CAD, No CUI, No ITAR. Controlled files stay protected.

Find help

Search every tip on this page. Pick a result to jump straight to that control.

    First things first

    A short path to your first result. Each step opens the next. Start anywhere, your progress is saved on this device.

    0 of 12 done
    1. Learn what gets shared What information can be shared, what stays protected, who decides.
      Open
    2. Read the proof map How a status reaches a reviewer without opening the controlled file.
      Open
    3. Review evidence readiness How many pieces of evidence are linked, how many are still open.
      Open
    4. Build a path in Flow From a source, to a review, to a reviewer, to the packet, in about a minute.
      Open
    5. Open your result packet One reviewed readiness packet, start to finish.
      Open
    6. Import a document Pull the readable fields from a file into an item. The file itself stays protected.
      Open
    7. Build your dashboard Add cards that each name one result you care about.
      Open
    8. Read the team roll-up See what teammates shared, most recent first.
      Open
    9. Review the inbox Consolidate related items, then approve a draft. Nothing sends on its own.
      Open
    10. Open the agents Read a pass rate, then run a path and watch each step.
      Open
    11. Run a simulation See pass or hold and an evidence gauge before a real run.
      Open
    12. File a request Tell the team what to build next. It saves on this device.
      Open
    The one idea

    Share the status. Keep the controlled file protected.

    A quality reviewer needs to confirm a supplier is qualified for a build step. Halcyon shares the qualification status and a short summary so the reviewer can act, and never opens the controlled drawing or inspection file to do it. The reviewer approves before anything is shared outside.

    Safe to share
    • Status, such as qualified, open, or at risk
    • The owner role and the build step it affects
    • A short plain-language summary
    • A link back to the controlled file in your own system
    Stays protected
    • The CAD drawing and the inspection file
    • Controlled and export-controlled content
    • Network topology and credentials
    • Anything a reviewer has not released yet

    Who decides: a named reviewer at the review gate. Nothing is shared outside until that person confirms it.

    Ask the assistant

    The assistant is like a junior analyst at a glass wall. It can read the status and the summary and link you to the controlled file, so a reviewer can open it and decide.

    Think of airport security. The screener can read the bag tag, the line, and why it paused. They do not open the bag. A person opens it, checks it, and decides whether it is good to go.

    Your result packet preview

    Readiness item IDMOCK-HALCYON-ITEM-001
    ModeDemo workspace
    Owner roleProgram readiness owner
    Evidence stateOn track
    Review gateNot reviewed

    No controlled data is included. Status and summary only.

    Open full result packet
    Two-minute lessons

    How this works

    What gets shared, and what stays protected?

    The status, owner role, class, timestamp, and a link back to the controlled file can be shared. The controlled file itself stays protected: the CAD drawing, CUI, ITAR content. Only a reviewer releases what goes outside.

    See what can be shared
    How does the assistant help?

    It reads the status and the summary and prepares a draft for review. It surfaces gaps, flags risks, and explains where the evidence stands. A reviewer reads it and signs off. Think of airport security: the screener reads the bag tag, and a person opens the bag.

    See it on the overview
    What is the result packet?

    The packet is your deliverable: one reviewed readiness item, start to finish. No controlled data inside, status and summary only. The review gate waits until a named role signs it off.

    Open a sample packet
    What can go wrong?

    Can the assistant open controlled files? No. The workspace is set up so it cannot.

    Who decides the packet is ready? A named reviewer at the gate.

    Can I see the controlled files here? No. They stay in your own system.

    See the overview
    What do Documents do?

    You import a file and Halcyon pulls the readable fields into editable cards. The controlled file never leaves your own system. The item you build feeds the result packet.

    Open Documents
    What is the dashboard for?

    It holds cards, and each card names one result you care about. Open a card to read the page that produced it. Share a card and a teammate gets a read-only copy on their own dashboard.

    Open your dashboard
    What is the team view?

    A read-only roll-up of every card a teammate chose to share, with the role it came from. Your personal cards stay personal. This is how personal and team context combine without crossing a line.

    Open the team view
    How does the inbox help?

    It reads the subject and status only, never the full contents. Related items from the same window group into one, with a draft reply that lists what was merged so nothing is missed. You edit and approve. Nothing sends on its own.

    Open the inbox
    What are agents?

    An agent runs a saved path. Its pass rate is a counted fact. A suggestion is an estimate, labeled as one. Run an agent to watch each step in order, and the run lands in the history so you can compare outcomes.

    Open the agents
    Why use the simulator?

    It shows the outcome of a run before you commit to a real one: pass or hold, an evidence-readiness gauge, the open items, and a confidence read. Most steps are counted facts. The human gate is the decision point.

    Open the simulator
    How do requests work?

    Tell the team what you need: a feature, a path, an agent, or something else. Add your role, the problem, and the outcome you want. It saves on this device. Every request goes to the team, and we cannot promise a response.

    File a request
    Replay any tour

    Show me how

    Each card opens the page and starts its walkthrough on arrival.

    Quick check

    Did it land?

    Why is this item waiting for a reviewer before it is shared outside? Pick the answer you believe. No grade, just learning.

    Where to start by role

    Pick the lane closest to your work. Each ends at the same reviewed deliverable.

    Program readiness owner

    You make the readiness call. Start at the proof map to see what is linked and what is open, then open the result packet to read the proof before you decide.

    Proof map · Result packet

    Field or quality reviewer

    You work signals by lane. Start at Signals to action to watch how a pressure becomes one routed deliverable, then build the path yourself in Flow.

    Signals to action · Flow

    Supplier or qualification lead

    You compare versions and evidence. Start at Evidence flow to follow a source to the gate, then check the value model for the recurring hours back.

    Evidence flow · Value model

    Executive or sponsor

    You want the whole picture in one read. Start at the Overview deck, then the value model to see the pilot framing and what it would measure.

    Overview deck · Value model

    Questions people ask

    Short answers to the ones that come up first.

    Can the assistant open controlled files?

    No. The workspace is set up so it cannot. The assistant reads the status and summary and prepares a draft. It cannot open a CAD, CUI, or ITAR file.

    Who decides the packet is ready?

    A named reviewer at the review gate. The packet waits until that person signs it off.

    Can I see the controlled files?

    No, they stay in your own system. Halcyon links to them. It does not store or open them.

    Do I need to set anything up?

    No setup in the demo. The live system reads the status and summary from your own system. No schema, no copy of the controlled file.

    Is any of this real data?

    No. This is a demo workspace on mock data. Every item id, owner role, and source is a sample shape only.

    Back to Halcyon overview Demo workspace · Mock data · status and summary only · No CAD · No CUI · No ITAR