Import Unknowns

When Opheleon imports your codebase, it doesn’t guess at things it can’t be sure of. Instead, it flags an unknown — an explicit note about something it couldn’t determine — and asks you to fill it in.

Unknowns are how you keep what Opheleon knows about your system accurate, with very little effort. The import does the heavy lifting on its own; you just supply the handful of things only your team knows.

Filling in gaps and correcting mistakes

There are two ways you steer what Opheleon learned:

• Fill in an unknown. Answer the question Opheleon flagged, supplying the context the code couldn’t show.
• Correct a mistake. If something it inferred is wrong, leave a comment with the correction.

Both stick. Your answers and corrections persist, so the next time Opheleon imports your codebase it already knows them — each import gets better instead of starting from scratch.

Why this matters

Code can show what the system does, but it can’t always explain why a decision was made or what the intended behavior is. Unknowns put that gap in front of you instead of burying it in a confident-sounding draft, so the system Opheleon plans against is one you can trust.