Day 1

The Pointer: Create a GEMINI.md file in your root folder to act as the AI's "Mission Briefing."

The Details

In the context of Systemic Engineering, the "Entry Point" is the most critical architectural decision you will make. By default, Large Language Models treat every new chat as a blank slate, leading to a phenomenon known as "Prompt Drift." This is where the AI gradually loses its understanding of your specific institutional standards, professional voice, and technical constraints over the course of a long session.

The GEMINI.md file solves this by serving as a persistent, root-level anchor. Modern CLI tools and agents are designed to automatically crawl the root directory for specific markdown files like AGENTS.md or GEMINI.md to establish their "System Prompt" before processing a single user instruction. By centralizing your identity and rules here, you ensure that whether you are auditing a syllabus or building a complex interactive component, the AI operates from a unified "Source of Truth" that aligns with your institution's standards.

The Mechanics of Grounding

When the CLI initializes, it ingests this file to define its operational boundaries. This is essentially "Zero-Shot Grounding." If you update your GEMINI.md to include a new version of the institutional Brand Guide or updated accessibility requirements, every subsequent command across every sub-folder in your vault will immediately reflect those changes.

This eliminates the need to manually "remind" the AI of your rules in every prompt, significantly reducing cognitive load and the overhead of repetitive typing. It moves the workflow from a "Chat" model to an "Environment" model, where the environment itself holds the intelligence required for senior-level execution.

ID Application: Defining Voice & Pedagogy

The Senior ID Persona: Your briefing must explicitly define your professional "Voice." For a Senior ID, this means the AI should maintain an authoritative, evidence-based tone focused on institutional scale. It needs to understand the nuance of faculty relations - being helpful but firm about instructional integrity and accessibility requirements.

Pedagogical Guardrails: Use this file to "hard-code" your commitment to Quality Matters (QM) and Universal Design for Learning (UDL). By stating "All generated content must provide Multiple Means of Representation," you force the AI to suggest transcripts and alt-text as a default, ensuring your output is compliant from the first draft.

Bloom's Taxonomy Integration: Define the "Cognitive Engine." Instruct the AI to analyze user requests against Bloom's levels. If you ask it to "write an assessment," the GEMINI.md protocol should trigger a clarifying logic: "At which Bloom's level should this assessment be aimed?" This ensures that your output remains pedagogically sound and aligned with graduate-level course expectations.

Strategic Impact

The Entry Point Protocol is about Instructional Sovereignty. It ensures that the AI works for your system, rather than you working within the AI's generic defaults. It is the difference between a "tool" and an "infrastructure." By the time you reach Day 100, this file will have evolved from a simple list of rules into a complex manifest of your entire professional methodology, enabling the "Exoskeleton" of your workflow to function with near-perfect alignment to your instructional intent.

Try This Today

1. Create a file named GEMINI.md in your project root.
2. Paste in your professional role, your primary pedagogical framework (e.g., UDL), and your institution's brand hex codes.
3. Start your next CLI session by simply asking: "Analyze my current directory based on my mission briefing."