FROM PROJECT TO PRESENCE
An Individualized Professional Learning & Creative Communication Intensive
Prepared by: Patricia Silva
Instructor: Dr. Jennifer Roble
September 2026
Although this jingle and video were initially created for Discussion 2, they directly embody the core problem and spirit of the From Project to Presence intensive. The piece was born from a very real academic bottleneck — the frustration of watching a solid, meaningful project remain hidden or forgotten on a shelf. By exploring storytelling, sound, and multimodality firsthand, this creative process tested the exact bridge the design proposes: moving from private completion to public visibility. It serves not just as a discussion response, but as a living example of how applied creativity helps professional knowledge travel and find its voice. As Check-In 3 moves from design into implementation, this piece remains a grounding reminder of why that bridge matters.
Check-In 2 established the professional learning design for From Project to Presence — its structure, pedagogical architecture, participant population, instructional sequence, and evaluation approach. This submission does not repeat that design. It moves forward.
A professional learning experience does not become sustainable simply because the design is strong. The next questions are practical: Who will lead it? How will participants be supported? When will decisions be made? Where will communication happen? What happens when the route becomes difficult? And what structures will allow the work to continue after the formal learning experience ends?
Check-In 3 documents how the experience will actually be led, implemented, supported, sustained, and improved over time. The shift is from design to implementation — from what the program should look like to how it will function in practice.
Why does this professional learning problem matter?
What should the professional learning experience look like?
How will the experience actually be led, implemented, supported, sustained, and improved?
Check-In 1 asked why the problem matters. Check-In 2 asked what the learning experience should look like. Check-In 3 asks how, when, where, and with whom that design can actually live. Leadership City is the environment where the design becomes observable practice. The sections that follow address each of those questions in turn.
What are we actually implementing — a program, or the conditions that allow people to move their work forward? That question shaped every decision in this check-in. Check-In 2 answered what the experience should look like. The design established an eight-day intensive, a T1–T2–T3 consultation architecture, a chiaroscuro activity evidence visualization, and a three-space model — private, learning, and public. Those decisions are previously established and are not repeated here.
Check-In 3 answers the next question: How will this experience actually be led?
"A well-designed professional learning experience does not implement itself. Leadership determines whether the design becomes practice — or remains a document."
The design establishes what should happen. Leadership determines whether it can happen in practice. That is where this submission begins.
From Project to Presence does not operate as a single event. It functions as an interconnected ecosystem of people, tools, spaces, and structures. Understanding how these elements relate to one another is the first step in understanding how the program is led.
Patricia Silva (Creator, Program Lead, Initial Facilitator, Technology Support). Future: qualified facilitators, operations support, guest professionals, community contributors.
8-day intensive. 8 structured hours. T1–T2–T3 Pedagnostic Consultations. Three-space architecture: Private / Learning / Public.
Leadership City — the digital implementation environment. Asynchronously accessible throughout each daily learning window.
Video, audio, camera, microphone, media library, project folders, collaboration, feedback infrastructure, and AI-assisted development tools.
Human decision-making retains authority. AI supports development and organization. Participants retain ownership of their projects.
These components are not independent. Leadership decisions affect all of them simultaneously. The sections that follow address each dimension of implementation in detail.
"The facilitator guides the route; the participant owns the work."
This principle is not decorative. It defines the operational logic of every leadership decision in From Project to Presence. Participant agency is not a feature of the program — it is the program's structural premise.
The facilitator does not create the participant's project for them. The participant enters the program with an existing project they already believe in. The program's function is to help them move that project — from private completion to public, professional presence.
Effective leadership in this context means creating the conditions in which participants can communicate their project, test it, revise it, position it, and move it into an authentic professional space. Leadership makes those conditions possible. It does not substitute for the participant's own work (Harapnuik et al., 2018; Vygotsky, 1978).
If leadership creates the conditions, the next question is who is responsible for creating and sustaining those conditions — and how that responsibility is distributed across the life of the program.
In the initial pilot, Patricia Silva holds all primary leadership functions. This is not a gap in the design — it is appropriate to the scale. The pilot will be small and facilitator-led, designed to gather implementation evidence before distributing responsibilities. As the program grows, leadership functions will be distributed by role and expertise, not by title alone.
Leadership is distributed by function. Project ownership remains with the participant at all times. Once responsibility is visible, implementation becomes a question of how those roles operate across time — and how they may be shared as the program grows.
Distributed leadership does not mean that all decisions are made collectively. It means that as the program grows, specific functions are held by people with the appropriate expertise and authority for those functions. In the pilot, all functions are held by the founder. Distribution is a scaling consideration, not a current operational requirement.
Patricia Silva: Program Lead, designated initial Facilitator, and Technology Support. Pilot infrastructure is being prepared. Implementation evidence will be gathered when the pilot is conducted.
Program Lead plus 1–2 Qualified Facilitators. Operations and Enrollment Support added. Community coordination begins. Guest professionals invited.
Distributed team by function. Facilitator team with appropriate qualifications. Technology, operations, community, and accessibility support distributed. Program Lead retains governance authority.
Future facilitators should hold preparation in Arts and Language/Communication, or possess an appropriate combination of expertise relevant to the interdisciplinary design of the program. Facilitation of From Project to Presence requires the ability to support participants across multiple representational modalities — visual, auditory, written, digital, and physical — without prescribing a single communication route.
These phases represent planning considerations informed by the program's current scale and resource context. They are not committed organizational milestones or guaranteed timelines. Implementation evidence gathered during the pilot will inform the pace and shape of any future distribution.
Participant ownership is not a pedagogical preference — it is a structural commitment that shapes every implementation decision. The participant enters the program with an existing project. The program does not assign a project. The participant's project is the curriculum anchor throughout the eight-day intensive.
The participant created it before entering the program. The program does not co-own, claim, or repurpose it. The participant retains full intellectual and creative ownership.
Which tools to use, which communication modality to pursue, which audience to address, and which channel to use for presentation — these are participant decisions, not facilitator prescriptions.
Audience feedback is invited by the participant. It informs reflection and revision. It does not determine competency, grade, or project value.
Work moves into the Online Vernissage or professional network only with participant approval. Private developmental evidence does not automatically become public.
A leadership model that removes participant agency in the name of efficiency undermines the program's core purpose. From Project to Presence exists to help professionals develop the capacity to communicate their own work — not to have that work communicated for them. Leadership creates the conditions. The participant does the work (Harapnuik et al., 2018).
With leadership responsibilities clear and participant ownership established, the next question is how the implementation architecture actually functions — what the eight days look like, where the consultations fit, and how the three spaces relate to one another.
The implementation architecture of From Project to Presence is built around three interlocking structures: the eight-day intensive, the T1–T2–T3 Pedagnostic Consultation cycle, and the three-space model. These were established in Check-In 2 and are briefly identified here as the operational foundation for the implementation decisions that follow.
8 consecutive days. 8 structured hours total. Approximately 30 minutes of instruction/modeling + 30 minutes of required applied project activity per day. Optional exploration may extend beyond the structured hour. Leadership City remains asynchronously accessible throughout each daily learning window.
Three private consultations integrated into the learning route. Each is approximately 15 minutes. T1: Baseline/Explore. T2: Development/Retune. T3: Transfer/Present. Comparable evidence is produced at each moment from the same authentic project.
PRIVATE: Activity Process Folder. LEARNING: Leadership City. PUBLIC: Online Vernissage / participant-approved professional presence. Private developmental evidence does not automatically become public.
The following timeline maps the participant experience across the eight-day intensive. Each day includes a structured one-hour experience — approximately 30 minutes of instruction and modeling, followed by 30 minutes of required applied project activity. Leadership City remains asynchronously accessible throughout each daily learning window, allowing participants flexibility in when they complete the required experience.
Implementation Status: IN DEVELOPMENT. This timeline is a planning instrument, not a validated implementation record. Adjustments may occur based on participant needs and facilitator observation. A route may be carefully designed and still encounter difficulty. The leadership question is what happens when the planned route no longer fits the reality.
The three Pedagnostic Consultations are the primary structured support moments within the eight-day intensive. They are not evaluative checkpoints. They are collaborative interpretation sessions in which the participant and facilitator review evidence together, identify what is working, and determine what should be retuned.
Between consultations, participants continue daily activities, access Leadership City resources, and may contact the facilitator with questions. The facilitator monitors activity evidence and may initiate additional support if early signals of difficulty are observed. Unscheduled consultations may be arranged when circumstances warrant.
All consultation notes and evidence are preserved in the participant's private Activity Process Folder. Consultation content is not shared publicly without participant consent. The folder is a private developmental record — not a public exhibition.
Implementation Status: IN DEVELOPMENT. Consultation scheduling and delivery logistics are being finalized within the Leadership City platform.
The three Pedagnostic Consultations are not evaluative checkpoints. They are structured support moments integrated into the learning route. Each consultation is approximately 15 minutes and is designed to help the participant and facilitator interpret evidence, identify what is working, and determine what should be retuned.
The participant introduces the existing project, completes baseline activities, explores available tools and representational routes, and produces initial evidence. The facilitator and participant establish a shared understanding of the project and the participant's starting point. Baseline evidence is preserved before targeted development begins.
The participant produces comparable project evidence after instruction and practice. The Dual Mirror then operates: the participant examines the evidence first through Learner Self-Observation, and the facilitator examines the same evidence through Instructor Interpretation. These are not two grades — they are two interpretive perspectives on the same activity evidence. AI may optionally organize and cross-reference the evidence to surface candidate patterns. Human Decision then determines the instructional route: retune, revise, continue, model, provide a resource, or change the route.
The participant communicates or presents the project in an authentic or transfer-oriented context. T3 asks a different question from T2: not what should be retuned, but whether the learning can transfer to an authentic or altered context. After T3, AI may organize a final longitudinal T1 ↔ T2 ↔ T3 comparison to support reflection and transfer analysis. That longitudinal report supports reflection and next developmental steps — it does not replace the Dual Mirror that occurred at T2. The participant reviews the full route, reflects on the arc of development, completes the final consultation, and prepares approved work for professional or public presence where appropriate.
Both perspectives examine the same evidence. They are not automatically merged. AI-generated comparisons are descriptive candidate patterns, not conclusions. Human Decision determines the consequential instructional route.
AI ORGANIZES. DUAL MIRROR INTERPRETS. HUMAN DECISION DETERMINES THE NEXT ROUTE.
The consultation is a dialogue, not a performance review.
The facilitator interprets evidence; the participant interprets meaning.
Retuning is a normal part of the route, not a sign of failure.
The participant retains decision-making authority over the project throughout.
Consultation notes are preserved in the private Activity Process Folder.
Implementation Status: IN DEVELOPMENT. The consultation framework is designed. Scheduling and delivery logistics are being finalized within the Leadership City platform.
What happens when the plan meets the reality of people's time, responsibilities, uncertainty, and different starting points? Professional learning must not become a one-time event that collapses when difficulty arises. The implementation plan includes a structured support logic for when participants encounter obstacles, when the route needs adjustment, or when the facilitator identifies a concern.
Participant encounters an obstacle, expresses uncertainty, or produces evidence that signals a need for support.
Facilitator reviews the participant's Activity Process Folder, recent activity evidence, and consultation notes to understand the nature of the difficulty.
Facilitator provides targeted support: additional resources, modeling, alternative approaches, or a revised activity prompt.
If the difficulty warrants it, an unscheduled consultation may be arranged. The participant and facilitator interpret the situation together.
The participant's route is adjusted — not abandoned. A new activity or approach is identified that serves the same learning purpose.
The participant attempts the revised activity. New evidence is preserved in the Activity Process Folder.
If difficulty persists after Step 6, the loop restarts at Step 1. The goal is sustained engagement, not a single correct path.
If illness, emergency, or significant personal circumstances interfere with participation, participants may contact the facilitator and an adjusted completion route may be arranged. Leadership City remains accessible asynchronously throughout each daily learning window, allowing participants flexibility in when they complete the required one-hour experience. The program is designed around accountability without unnecessary policing.
Support cannot function if participants do not know where to ask, who will respond, or what happens next. That is the purpose of the communication plan.
Effective implementation requires intentional communication. Without it, participants do not know what to expect, where to ask questions, or how to access support. The following plan identifies what is communicated, to whom, by whom, when, through which channel, and for what purpose. Questions and feedback are routed through Leadership City or directly to the facilitator.
All communication channels are subject to Leadership City platform availability.
Even a coherent plan operates inside real constraints. Time, technology, readiness, access, and competing priorities must therefore be treated as implementation conditions — not as exceptions.
Leadership City is the digital implementation environment for From Project to Presence. It is not a generic learning management system. It is being developed specifically to support the pedagogical architecture of this program — including the T1–T2–T3 consultation cycle, the Activity Process Folder, the three-space model, and the professional community.
Daily learning prompts, instructional content, activity guides, resource library, and facilitator-curated materials.
Status: IN DEVELOPMENT
Private Activity Process Folder, project drafts, recordings, evidence archive, consultation notes, and reflection space.
Status: IN DEVELOPMENT
Messaging, calendar, meeting scheduling, notifications, and feedback infrastructure.
Status: IN DEVELOPMENT
Video recording, audio recording, camera, microphone, screen sharing, uploaded media, and project visuals.
Status: IN DEVELOPMENT
Participant-approved public exhibition space for final artifacts. Publication requires explicit participant consent.
Status: IN DEVELOPMENT
Profiles, project updates, community discussions, events, workshops, and resource sharing.
Status: PLANNED
Leadership City is being developed through a human-directed, AI-assisted workflow. Patricia Silva holds final authority over all pedagogical, design, and implementation decisions. ChatGPT provides design dialogue, reasoning support, drafting, and coding assistance. Gemini / Google AI Studio provides AI-assisted platform development support. AI tools are development supports — not program leaders.
Time is a significant implementation consideration in professional learning. The design of From Project to Presence acknowledges this directly. The program does not ask participants to find time — it asks them to protect one hour per day for eight consecutive days.
Instruction & Modeling
Guided instruction, facilitator modeling, and structured learning content delivered through Leadership City.
Applied Project Activity
Required applied activity directly connected to the participant's own project. This is not a generic exercise — it is project-specific work.
Extended Exploration
Participants may choose to extend their engagement beyond the structured hour. Leadership City remains accessible asynchronously throughout each daily learning window.
Leadership City remains accessible asynchronously throughout each daily learning window, allowing participants flexibility in when they complete the required one-hour experience. Participants are not required to complete the experience at a fixed time. They are required to complete it within the daily window.
The program is designed around accountability without unnecessary policing. Participants are adults with professional responsibilities. If illness, emergency, or significant personal circumstances interfere with participation, participants may contact the facilitator and an adjusted completion route may be arranged. The goal is sustained engagement — not rigid compliance.
This approach is consistent with professional learning design principles that recognize adult learners require flexibility, relevance, and autonomy to sustain engagement (Learning Forward, 2022; Harapnuik et al., 2018).
Resources are not a footnote to implementation planning. They are a condition of it. The following table documents the resources required to implement From Project to Presence. The pilot is intentionally small and facilitator-led. Resource needs will grow as the program scales. Founder-contributed labor is not described as having no economic value merely because it is not currently billed to the pilot.
Potential future cost categories may include API usage, hosting, storage, domain, payment processing, facilitator compensation, technical support, operations, community/content coordination, accessibility services, and guest honoraria where applicable. Exact future costs are not projected here. These are planning categories, not budget commitments.
Responding to difficulty keeps the program moving today. Sustainability asks whether the structures can keep it moving tomorrow — and whether the people and resources required to do so are honestly accounted for.
From Project to Presence is currently a founder-led initiative. Organizational support in the pilot phase is provided primarily by Patricia Silva across all functions. This section documents the support structures that exist, those in development, and those planned for future implementation.
Patricia Silva provides all program leadership functions: conception, design, facilitation, technology support, and governance. This is appropriate for the pilot scale.
The Leadership City platform is being developed through a human-directed, AI-assisted workflow. Current tools include ChatGPT, Google Flow, and Suno. The platform is in active development.
Leadership City provides the digital learning environment. Asynchronous access supports participant flexibility. Materials are facilitator-developed.
The pilot is intentionally small. At larger scale, responsibilities will need to be distributed among a team. Exact staffing ratios and enrollment thresholds are not projected here. Scaling decisions will be informed by implementation evidence gathered during the pilot.
Realistic implementation planning requires honest identification of likely barriers. The following barriers represent implementation risks identified through the current design, resource context, participant needs anticipated in the pilot, and the operational conditions of the developing platform. They will be revised as actual implementation evidence becomes available. Naming them is not pessimism. It is the difference between a plan that can adapt and one that cannot.
Responding to difficulty keeps the program moving today. Sustainability asks whether the structures can keep it moving tomorrow — and whether the initiative can outlast any single person's capacity to hold it together.
From Project to Presence is designed for adult professionals with diverse backgrounds, professional contexts, and life circumstances. Accessibility and equity are not afterthoughts — they are implementation responsibilities.
Leadership City remains accessible asynchronously throughout each daily learning window. Participants are not required to complete activities at a fixed time. This reduces barriers related to work schedules, caregiving responsibilities, and time zones.
Participants choose which communication modalities to use for their projects. No single representational route is required. This supports participants with different abilities, preferences, and access to tools.
If illness, emergency, or significant personal circumstances interfere with participation, an adjusted completion route may be arranged. The program does not penalize participants for circumstances outside their control.
All developmental evidence is private. Participants are not required to make their work public before they are ready. Public presence is participant-controlled.
Accessibility planning will be formalized before the pilot cohort is enrolled. Current commitments reflect design intentions; formal accessibility review is planned.
The workshop ends. The learning environment does not. After the eight-day intensive, participants retain access to Leadership City. The program is designed as a workforce development initiative supported by an ongoing professional community — not as a one-time event that disappears when the final consultation concludes.
Participants retain access to their Activity Process Folder, project materials, and the Leadership City learning environment after the intensive concludes.
Leadership City may support a professional network where participants maintain profiles, share project updates, connect with other professionals, and access ongoing resources. Status: PLANNED.
Participants who choose to publish their final artifact may do so through the Leadership City Online Vernissage — an authentic-audience experience. Publication requires participant approval. Status: IN DEVELOPMENT.
A newsletter and periodic events may extend community connection beyond the intensive. Status: PLANNED.
Guest professionals and participants may contribute stories about moving projects into professional life. These contributions build a growing community knowledge base. Status: PLANNED.
Additional workshops and community meetings may be offered to sustain engagement and professional development beyond the initial intensive. Status: PLANNED.
Sustainability requires intentional leadership. The sections that follow address who maintains these structures and how ownership may become more distributed as the program grows.
From Project to Presence is designed as a workforce development course supported by an ongoing professional community. The intensive is the entry point — not the entirety of the experience. Leadership City may support a professional network where participants can maintain professional presence, share project updates, and connect with other professionals long after Day 8.
Participants may maintain professional profiles, share project updates, discuss ideas, participate in debates, connect with other professionals, access workshops, attend meetings, receive event information, share resources, and discover project stories.
Status: PLANNED
A participant-approved public exhibition of final artifacts. An authentic-audience experience. Not grading. Not a popularity contest.
Status: IN DEVELOPMENT
Guest professionals and participants may share stories about taking a project into public or professional life — including communication decisions, challenges, presentations, recognition, and lessons learned. These stories contribute to a growing community knowledge base.
Status: PLANNED
YouTube and a dedicated Facebook community may extend reach beyond Leadership City. Leadership City remains the central learning and professional-community environment.
Status: PLANNED
A newsletter and periodic events may sustain community connection and professional development beyond the intensive.
Status: PLANNED
The professional community is not a passive archive. It requires active leadership to remain relevant and safe. Community coordination will be a distinct leadership function as the program grows. Participant contributions to the community are voluntary. Private developmental evidence does not automatically become community content.
What remains after the eight days are over? That is the sustainability question — and it is not answered by good intentions. Sustainability requires intentional planning for who maintains the program's structures, how leadership is distributed as the program grows, and how the community continues to generate value for participants over time.
Participants retain access to Leadership City, their Activity Process Folder, and community resources after the intensive concludes. The learning environment does not close on Day 8.
An ongoing professional community sustains participant engagement, project visibility, and professional connection beyond the intensive. Leadership City is the central environment.
A growing library of project stories — contributed by participants and guest professionals — creates a self-sustaining knowledge base that grows with each cohort.
Participants who complete the program may invite or refer other professionals. Community growth through authentic professional connection is more sustainable than marketing alone.
Leadership functions are distributed by expertise and role as the program grows. The scaling plan is designed to reduce single-person dependency over time.
Future sustainability requires a revenue model. This is a planning consideration, not a current commitment. Potential models include enrollment fees, organizational partnerships, and community membership.
Sustainability is not a feature that can be added later. The sections that follow address what prevents the initiative from disappearing — and what the next steps look like from here.
A significant implementation risk in professional learning is not necessarily poor design, but loss of continuity after the initial learning experience. A program may be well-designed, well-facilitated, and well-received, and still disappear after its first cohort because no one planned for what comes next. From Project to Presence is designed to resist that failure mode.
Participants retain access to Leadership City after the intensive. The learning environment does not close. The community does not dissolve.
As the program grows, leadership functions are intended to be distributed by role and expertise, reducing dependence on any single individual's continued availability.
Participants become community members, not just alumni. They may contribute project stories, invite other professionals, and participate in ongoing events. The community generates its own value over time.
The program's design, governance, and implementation logic are documented. If leadership transitions, the documentation provides continuity.
The program does not pretend that founder-contributed labor has no cost. Future sustainability requires a revenue model. Planning for that model begins now, not after the program has already grown beyond founder capacity.
Each cohort generates implementation evidence. That evidence informs the next iteration. The program improves through use, not through speculation.
Sustainability is not a feature that can be added later. It must be designed into the program from the beginning. From Project to Presence is designed with sustainability as a structural commitment — not as an aspiration. The sections on distributed leadership, community, and resource planning are not supplementary. They are part of the implementation plan (McChesney et al., 2012; Learning Forward, 2022).
From Project to Presence does not use the Human Pipeline musical-tone visualization. Its developing visual metaphor is drawn from the visual arts: tonal light and shadow — chiaroscuro / value.
Chiaroscuro is a descriptive visualization layer for observable activity evidence. It is not a score, grade, diagnostic instrument, or classification of the participant.
Early or minimal observable activity. The participant is beginning to engage with the project and the tools. Evidence is sparse or initial.
Observable activity is developing. The participant is producing evidence of engagement, exploration, and early application.
Observable activity is substantive. The participant is producing evidence of development, revision, and intentional communication decisions.
Observable activity reflects transfer. The participant is producing evidence of authentic communication and project presence in a real or transfer-oriented context.
"This visualization describes ACTIVITY EVIDENCE. It does NOT classify the participant. We measure the activity, not the person."
AI may organize observable evidence into the visualization. The Dual Mirror — Learner Self-Observation and Instructor Interpretation — determines instructional meaning. AI-generated visualizations are descriptive candidate patterns, not conclusions.
The exact calculation model for this visualization is IN DEVELOPMENT / NOT VALIDATED. No scoring formula has been invented or validated. The visualization is a developing concept — a planning instrument for understanding activity evidence, not a finished grading tool.
AI may organize and compare selected activity evidence. Human decision determines what that evidence means. The facilitator interprets the visualization in consultation with the participant. The participant retains interpretive authority over the meaning of their own work.
WE MEASURE THE ACTIVITY, NOT THE PERSON.
AI COMPARES EVIDENCE. HUMAN DECISION DETERMINES MEANING.
This governance principle is not a disclaimer — it is a structural commitment. AI tools play a meaningful but bounded role in From Project to Presence. Human professionals retain authority over all pedagogical, leadership, implementation, and evaluative decisions.
Originator, author, program lead, and final decision authority. Responsible for all intellectual conception, pedagogical design, leadership decisions, implementation decisions, interpretation, and professional judgment.
Primary AI assistant. Supported dialogue, brainstorming around Patricia Silva's ideas, organization, drafting assistance, language refinement, research and citation navigation, critical review, prompt development, coding assistance, and debugging. Did not originate the project or hold decision-making authority.
AI-assisted code generation, debugging, and platform implementation support for Leadership City, under Patricia Silva's direction. Did not originate the project or hold decision-making authority.
Gamma: presentation organization, formatting, and layout. Suno: AI-assisted audio and music creation. Other tools used only for specifically disclosed functions. None hold pedagogical, leadership, or evaluative authority.
This table describes AI governance within the From Project to Presence program — what AI may and may not do with participant activity evidence. For disclosure of how AI was used during the development of this submission, see the Generative AI Disclosure and AI Use Disclosure — Extended sections.
The following table documents the current implementation status of From Project to Presence components. This is a developmental check-in. Showing what is unfinished is intentional. At this stage, making uncertainties visible is more academically honest than claiming completion that does not yet exist.
The following audit documents the current state of this submission against the Check-In 3 assignment requirements. This is not a self-congratulatory checklist — it is a transparent accountability instrument.
This submission addresses all required Check-In 3 areas. Where components are not yet implemented, they are labeled IN DEVELOPMENT or PLANNED. No planned feature is described as already functioning. No prototype is presented as validated implementation evidence.
Check-In 3 documents the leadership and implementation plan for From Project to Presence. The next phase is moving from planning to observable practice. The following steps represent the immediate priorities before the pilot cohort is enrolled.
Complete the core infrastructure: participant workspace, daily learning environment, T1–T2–T3 consultation scheduling, Activity Process Folder, and communication tools. Status: IN DEVELOPMENT.
Finalize data ownership, evidence use, and participant rights documentation before any participant is enrolled. Status: IN DEVELOPMENT.
Complete a formal accessibility review of the Leadership City platform. Identify and address gaps before pilot enrollment. Status: PLANNED.
Identify and enroll the initial small pilot cohort. The pilot is intentionally small — designed to generate implementation evidence, not to demonstrate scale. Status: PLANNED.
Facilitate the first eight-day intensive. Preserve implementation evidence throughout. Document what works, what needs retuning, and what was not anticipated. Status: PLANNED.
After the pilot, review all implementation evidence. Retune the design, the platform, and the leadership approach based on what was observed. Status: PLANNED.
From Project to Presence is not a finished product. It is a developing professional learning initiative grounded in a clear problem, a coherent design, and an honest implementation plan. The next step is practice. And practice will generate the evidence that no planning document can replace.
This submission is built on a commitment to transparency that runs through every section. The following statements summarize the transparency commitments that govern From Project to Presence as a developing initiative.
Every component of this submission is labeled: LIVE, IN DEVELOPMENT, or PLANNED. No planned feature is described as already functioning.
Leadership City is in development. The chiaroscuro visualization has not been validated. The pilot has not yet run. These facts are stated directly, not obscured.
Generative AI tools were used as development supports. Their roles are documented. The author retains full responsibility for all academic work.
Founder-contributed labor is not described as having no cost merely because it is not currently billed to the pilot. Future sustainability requires honest resource planning.
Participants retain ownership of their projects. Private developmental evidence does not automatically become public. Audience feedback does not determine competency, grade, or project value.
AI does not possess leadership or educational decision-making authority. Human professionals retain authority over all pedagogical, leadership, implementation, and evaluative decisions.
Transparency is not a section of this submission. It is the condition under which this submission was written.
The conception and intellectual development of From Project to Presence are my own. I developed the problem, instructional architecture, participant-centered structure, T1–T2–T3 route, Pedagnostic Consultation model, Leadership City concept, activity-evidence approach, leadership decisions, implementation strategy, and sustainability plan.
I used ChatGPT as my primary AI assistant throughout the development process — conversationally, to help me organize and articulate ideas I had already developed, structure academic content, build tables and matrices, refine English grammar and syntax, organize citations and references, navigate research, review coherence, develop prompts, and assist with coding and debugging. I frequently revised, rejected, redirected, or expanded its suggestions. ChatGPT did not have authority to make pedagogical, leadership, implementation, or evaluative decisions.
Gemini / Google AI Studio was used primarily to support code generation, debugging, and implementation of Leadership City under my direction. Gamma was used to organize and format the presentation. Suno was used for AI-assisted audio and music creation where applicable.
All final decisions regarding pedagogy, leadership, implementation, interpretation, content selection, project direction, and professional judgment are mine. Generative AI assisted with the development and production process. I retained intellectual authorship, academic responsibility, pedagogical authority, and final decision-making authority throughout.
— Patricia Silva
A detailed documentation of AI-supported functions, tools, and human oversight is provided in the AI Use Disclosure — Extended section.
AI USE LEVEL 2 — AI-ASSISTED
The following documents the specific functions generative AI supported during the development of this submission and the broader From Project to Presence initiative. This extended disclosure is provided in addition to the short disclosure included earlier in the presentation.
From Project to Presence — including its problem framing, participant-centered premise, instructional architecture, T1–T2–T3 route, Pedagnostic Consultation model, Activity Process Folder, Leadership City concept, three-space Private / Learning / Public architecture, Online Vernissage, Chiaroscuro / Value activity-evidence concept, professional-community design, leadership structure, implementation logic, communication plan, sustainability strategy, and AI governance principles — originated with Patricia Silva. These concepts were not generated by AI. ChatGPT assisted Patricia Silva in articulating, organizing, testing, refining, and developing them through conversation.
AI did not originate From Project to Presence or any of its core concepts
AI did not independently choose the instructional philosophy or leadership model
AI did not make pedagogical, leadership, implementation, or evaluative decisions
AI did not have final authority over any decision in this project
AI did not evaluate participant work or determine educational meaning
AI did not replace Patricia Silva's professional judgment at any stage
Patricia Silva reviewed, questioned, accepted, rejected, modified, or redirected AI-supported outputs throughout the development process. All final decisions regarding pedagogy, leadership, implementation, interpretation, content selection, project direction, and professional judgment are hers. Generative AI assisted with the development and production process; it did not replace her authorship or professional judgment.
— Patricia Silva, September 2026
Designing a professional learning experience is one kind of intellectual work. Planning how to lead, implement, sustain, and improve it is another. Check-In 3 required me to move from the architecture of the program to its operational reality — and that shift revealed things that the design phase could not.
The most difficult questions were not about structure. They were about honesty. How do I describe what is built without overstating it? How do I plan for sustainability without pretending I know what the program will look like at scale? How do I acknowledge the economic value of my own labor without claiming resources I do not yet have? The answers required a kind of disciplined transparency that I want to carry into the implementation itself.
From Project to Presence is designed to help participants make their work visible. This check-in required me to make my own planning visible — including its uncertainties, its gaps, and its genuine commitments. That felt like the right kind of preparation.
The pilot must generate real implementation evidence — not just confirm the design.
Leadership City must be functional before participants are enrolled.
Privacy and accessibility documentation must be completed before the pilot begins.
The program's sustainability depends on honest resource planning, not optimistic projection.
Distributed leadership is a planning commitment, not a future aspiration.
The participant's project is always the center. Everything else is infrastructure.
When I began this stage of the PLLP, I was still thinking primarily about the structure of a workshop. As I worked through the implementation questions — who leads, how communication flows, what happens when things become difficult, how the program sustains itself after Day 8 — I found myself thinking less about the program and more about the people inside it. Implementation is not the moment when the plan stops changing. It is the moment when leadership, evidence, people, time, resources, and context begin to test whether the plan can actually live.
A project does not become present simply because it exists. A professional may have spent years developing something meaningful — a body of work, a method, an idea, a practice — and still not know how to make its value visible to an audience that matters. Within the scope of this professional-learning design, that gap is treated primarily as a communication and positioning problem rather than as evidence of limited talent or potential. And it is a leadership problem, because creating the conditions in which people can close that gap requires intentional, sustained, human-centered leadership. From Project to Presence is my attempt to address that problem in a structured, honest, and participant-centered way.
The design is not finished. The platform is not finished. The pilot has not yet run. But the architecture is coherent, the governance is clear, and the leadership logic is grounded in a principle I believe in:
"The facilitator guides the route. The participant owns the work."
Leadership makes the conditions possible. The participant does the work. The next source of knowledge will not come from planning. It will come from practice.
Why does this professional learning problem matter?
What should the professional learning experience look like?
How will the experience actually be led, implemented, supported, sustained, and improved?
The implementation environment where the design becomes observable practice.
Prepared by Patricia Silva | EDLD 5389 — Developing Effective Professional Leadership | Dr. Jennifer Roble | September 2026
Harapnuik, D., Thibodeaux, T., & Cummings, C. (2018). COVA: Choice, ownership, voice, and authenticity. Self-published.
Learning Forward. (2022). Standards for professional learning. https://learningforward.org/standards/
McChesney, C., Covey, S., & Huling, J. (2012). The 4 disciplines of execution: Achieving your wildly important goals. Free Press.
Vygotsky, L. S. (1978). Mind in society: The development of higher psychological processes. Harvard University Press.