Meet Noea Code

Noea Code (Noea for short) helps you understand and decide how your software behaves when you build with AI. You write down requirements, a coding Agent changes the code, and you use implementation explanations, evidence, and concerns to check whether the result meets your expectations.

Start with a single rule in an existing project. A product behavior, an architectural constraint, or an algorithm requirement can all be your first intent.

Intent means the requirements you want the software to keep satisfying. They remain relevant after a feature is finished. When you decide to change its behavior, you change the corresponding words. You do not need to describe the entire application: start with what matters to you.

Connect intent to implementation

Suppose you are building a daily check-in app and write:

Give the user a reward after 7 consecutive days of check-ins.

This sets the condition for a reward, but leaves several choices open: what counts as a day, what happens after a missed check-in, and what kind of reward to give. The Agent still has to make those choices when implementing the rule.

Noea connects the sentence to an explanation of the implementation. You can read how the code counts days, open the code references or test material behind the explanation, and identify unmet requirements or choices worth discussing. If you decide that a day must follow the user's local calendar date, add that decision to the intent so future work has to respect it.

Know the three kinds of content

Intent documents are Markdown files. You can track them with Git or edit them in another editor. Noea stores implementation explanations separately and displays them in margin notes. Some English interface labels call the intent documents Source; this is distinct from the code in the implementation folder.

Follow the everyday workflow

1. Clarify the intent. Write it directly, or discuss it with the Agent and review the proposed wording.
2. Implement and understand. Let the Agent work, then investigate the implementation and read the explanation, evidence, and concerns.
3. Record your decisions. Ask about a specific paragraph, add requirements you want to keep, and continue implementing and checking.

If the code already exists, write the requirement you want to check and run Explain. If it still needs implementing, use a chat or the Realize action.

You can accept a choice you understand without turning every implementation detail into a lasting requirement. See Read explanations and evidence for help deciding what belongs in your intent.

Understand Noea's role and the Agent's role

Noea provides the workbench for writing documents, discussing decisions, reviewing changes, and reading explanations. The Agent reads the project, calls tools, and changes code. Choose a supported Agent and use the models and sign-in methods it offers.

In Noea's proposal workflow, changes to your intent documents require your decision. You can edit and accept a proposal, or dismiss it. Code changes and commands depend on the Agent's capabilities and permission settings.

Implementation explanations do not replace tests or hands-on use. Check the evidence for important behavior and verify it as needed.

Start with a small, meaningful question

Choose something narrow with an observable result: when a reward is issued, how insufficient stock is handled, or a constraint an API must obey. You can keep using your existing development process for the rest of the project.

Next, install and get ready, then follow your first workflow.