Concept
Learn the vocabulary, model, history, and boundary. Explain the idea in plain language and distinguish it from nearby ideas.
Learning method
ARCTURA learning moves through four stages: understand a concept, examine a case, make an artifact, and improve it through review. The artifact is where explanation becomes accountable practice.

The cycle
The cycle can fit a 30-minute exercise or a multi-week project. What changes is the depth of evidence and review—not the basic discipline.
Learn the vocabulary, model, history, and boundary. Explain the idea in plain language and distinguish it from nearby ideas.
Examine a bounded situation. Separate observations from interpretations and compare more than one plausible reading.
Apply the concept to real structure: a decision record, domain model, review cycle, evidence note, or other object.
Invite a specific challenge. Record what changed, what remains unresolved, and what should trigger another review.
Review rubric
| Dimension | Review question | Evidence of strength |
|---|---|---|
| Purpose | Is the question bounded and worth answering? | The artifact names a decision, audience, use, and excluded scope. |
| Structure | Does the model fit the problem? | Important entities, options, roles, relationships, or stages are explicit. |
| Evidence | Can claims be traced and challenged? | Sources are identifiable; observation, interpretation, and assumption are distinct. |
| Alternatives | What else could be true or done? | The artifact includes competing options, counterexamples, or stakeholder views. |
| Boundary | What does this work not establish? | Uncertainty, missing evidence, permissions, and professional limits travel with it. |
| Revision | What would reopen the work? | An owner, next action, review date, or observable trigger is named. |
Review protocol
A useful review identifies the exact element under challenge, explains why it matters, and proposes evidence or a test. “I disagree” is a starting signal, not a complete review.
Restate the artifact's purpose and strongest claim before challenging it. Confirm that you are reviewing the intended work.
Establish shared contextName one unsupported assumption, omitted alternative, ambiguous term, weak handoff, or boundary that needs attention.
Make critique actionableRecord the response: accepted change, rejected change with rationale, or unresolved question with a next test.
Preserve the decision trailWorked review
Suppose a reviewer says, “This model is too simple.” A useful response asks which required question the model cannot answer. The reviewer identifies that the model records a decision and its evidence but cannot represent when a cited source was superseded. The learner adds source lifecycle state and a replacement relationship, updates a sample record, and reruns the competency question.
The revision note preserves the original gap, the specific challenge, the accepted change, and the test that now passes. If the learner rejects the change, the record should explain why the detail is outside the model's stated purpose. Either outcome is more useful than resolving the exchange through confidence or preference.
Use and limits
These materials support independent learning and peer review. They do not certify competence, replace supervised practice, or authorize engineering, legal, medical, financial, security, or other professional decisions. Match review depth to consequence.