Working with Phoebe

Phoebe uses the same Lumicron API reference as this guide. Documentation describes API behavior; current project facts come from project inspection tools. Neither source substitutes for the other.

Reference questions

Ask about an API symbol or a behavior, for example Join, endpoint straight lengths, route profiles, or simulation bench inputs. Phoebe can retrieve relevant sections locally. API lookup does not execute scripts, change the project, or require a commercial connection. An answer should identify the canonical spelling and the reference section used.

Project questions

To explain why a particular route or placement differs from your intent, Phoebe needs the actual source and relevant layout or schematic facts. Enable the relevant context in Assistant Settings. A documentation example cannot establish which ports, parameters, or model your project actually uses. Missing metadata should be reported as unavailable, not guessed.

Actions and reasoning

Apple’s on-device model handles supported simple questions. More involved tasks may use the installed local model or a connected commercial service through Phoebe’s routing. Local reference lookup remains available to all of those backends. Source edits and execution follow Lumicron’s action permissions and review workflow; a proposed action is not a completed action.

For a diagnosis, include the observed result and intended behavior, let Phoebe inspect the relevant evidence, review any proposed change, and check the regenerated layout. A generated layout is not fabrication approval or proof that a physical model matches the foundry device.