Inspect and clarify
Understand the question, source context, existing capability and limits before proposing a change.
Methodology
Make the work understandable and reviewable.
Inspect the current system, identify the responsible owner, define a bounded change and validate what actually changed. Keep evidence and human decisions connected throughout.
From question to reviewed result.
Use the established owner
Keep shared intelligence, project planning, private access and execution with their responsible components.
Implement and verify
Make a bounded change and check its behavior, evidence, accessibility and affected integrations.
Review and authorize
Present results and open gaps. People decide whether consequential next steps are appropriate.
Evidence has boundaries.
Core 12 provides shared deterministic intelligence where its contract applies. Product behavior, scientific validity, release readiness and access acceptance require their own checks. A successful software test does not prove a clinical or scientific conclusion.
Software discovery and a proposed Blueprint do not authorize development, payment, private access or release. Each transition retains the established owner and human review.