docs(aurelius): implement agentic inversion protocol phase 1

[projectedanx]

This commit implements Phase 1 of the Agentic Inversion Protocol as outlined for the META_ARCHITECT_INTELLIGENCE_PROJECT_AURELIUS architecture.
It introduces documentation surrounding the Strategic Integration Project Manager persona, transitioning from a Prompt->Output model to an Agentic Telemetry Loop (Structural Mapper).

Changes include:

• README.md: Added section detailing the Agentic Inversion Protocol and Project Aurelius value proposition.
• LESSONS_LEARNED.md: Documented insights regarding Paraconsistent Mapping and shifting from solving to structural mapping.
• COGNITIVE_CONTRACT.md: Defined adherence to the VULCAN framework and the Mereological Mandate (CFDI constraints).
• DASL.md: Mapped the new Operational Workflow semantics (SPZ-Zeta).
• SymbolicScar.json: Added a new scar entry logging the resolution to narrative ambiguity via the PM Persona structure.

---

PR created automatically by Jules for task 12311717304145919096 started by @projectedanx

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Code Review

This pull request introduces the Agentic Inversion Protocol, adding comprehensive documentation for the VULCAN framework, the SPZ-Zeta operational workflow, and strategic lessons learned regarding paraconsistent mapping. It also updates the README and SymbolicScar.json to reflect these architectural shifts. Feedback was provided regarding a technical inaccuracy in the README, specifically pointing out that the reference to an Angular-style component file is inconsistent with the project's technology stack and implementation status.

[gemini-code-assist]

The reference to app.component.ts appears to be incorrect for this project's technology stack. The repository primarily uses Python and mentions Next.js (which typically uses .tsx or .js), whereas .component.ts is an Angular convention. Additionally, stating that the persona is 'integrated' while also being 'conceptual' is contradictory. It would be clearer to state that the persona has been 'introduced' or 'defined' as part of the protocol.

Suggested change

	In accordance with the Agentic Inversion Protocol (Phase 1), we have integrated the **Strategic Integration Project Manager** persona (operational within `app.component.ts` conceptually) to shift from a traditional "Prompt -> Output" paradigm to an **Agentic Telemetry Loop**.
	In accordance with the Agentic Inversion Protocol (Phase 1), we have introduced the **Strategic Integration Project Manager** persona to shift from a traditional "Prompt -> Output" paradigm to an **Agentic Telemetry Loop**.

References

1. Documentation should accurately reflect the project's technology stack and implementation status. Referencing non-existent files or using conventions from unrelated frameworks can lead to developer confusion.