# ❓ FAQ — Frequently Asked Questions ## What is this site? This is a portfolio and thinking space. It collects projects, writing, and reference documents that reflect how I approach software design, AI-assisted development, and system architecture. ## Is this a framework or product? No. The ideas here are not a packaged framework or a tool you install. They are principles, patterns, and experiments that can inform how tools and systems are designed. ## Who is this for? Primarily: - engineers and architects working on complex or long-lived systems - teams exploring AI-assisted development beyond prompt hacking - people curious about how software design changes when generation becomes cheap ## Is everything here meant to be followed exactly? No. Most documents are orientation, not instruction. They describe how decisions are reasoned about, not rules that must be obeyed. ## Why so much emphasis on evidence and verification? Because explanations are cheap—especially with AI. Evidence creates shared reality and prevents misplaced confidence. ## Is this content stable? Some parts are intentionally stable; others are evolving. Where possible, documents label their maturity and confidence level so readers can judge how much weight to give them. ## Can I reuse these ideas? Yes. The intent is openness and reuse. Attribution is appreciated, but the bigger goal is to reduce repeated mistakes and encourage clearer thinking. ## Why do some ideas appear unfinished or revisited? Because in non-deterministic systems, one outcome isn't enough to judge an idea. This work favors observing multiple attempts before drawing conclusions.