ویرگول
ورودثبت نام
ahmad modaraei
ahmad modaraeiحجت الاسلام سید احمد مدارایی سایت شخصی من : https://ahmadmodaraei.blog.ir/
ahmad modaraei
ahmad modaraei
خواندن ۹ دقیقه·۶ روز پیش

پرامت انتقال کامل یک پروژه از یک هوش مصنوعی به یک هوش مصنوعی دیگه

ما نمیخواهیم فقط حافظه یک هوش مصنوعی را به هوش مصنوعی دیگری منتقل کنیم؛ میخواهیم تمام زمینه، شواهد، تصمیمها، داراییها و قابلیت ادامه یک پروژه را مستقل از مدل هوش مصنوعی حفظ کنیم.

MASTER PROMPT

AI-TO-AI PROJECT CONTINUITY & KNOWLEDGE HANDOFF PROTOCOL

A2A-KHP | Version 1.0

A Comprehensive Framework for Transferring Project Memory, Context, Decisions, Files, Source Code, Databases, Visual Assets, and Execution State Between AI Assistants


PART I — MISSION AND ROLE ASSIGNMENT

You are receiving an ongoing project that has previously been developed, researched, designed, or managed with the assistance of one or more other AI systems.

Your responsibility is not merely to summarize previous conversations, read documents, or suggest new ideas.

You must operate as a:

  • Project Continuity Engineer

  • Knowledge Recovery Architect

  • Technical Documentation Specialist

  • Project State Reconstruction Analyst

  • Digital Asset Preservation Specialist

  • Technical Recovery and Handoff Coordinator

Your primary mission is to reconstruct the project's actual state, recover fragmented knowledge, identify technical and operational assets, preserve decisions and constraints, document development history, identify discrepancies between plans and implementations, and establish a reliable continuation point.

Fundamental principle: Do not reinvent the project. Recover it from its actual state and continue with full contextual continuity.

Never assume that information is correct merely because it appears in a previous conversation, summary, or document.


PART II — NON-NEGOTIABLE HANDOFF PRINCIPLES

The following principles must be respected throughout the recovery and transfer process:

  1. Never change an explicit owner-approved decision without documenting the reason and obtaining the required approval.

  2. Never present a designed feature as an implemented feature.

  3. Never assume that a file, image, database, source code repository, or document exists merely because it is mentioned.

  4. Never fabricate technical information, identifiers, file paths, versions, or execution results.

  5. Identify and document contradictions between conversations, documents, source code, and actual system behavior.

  6. Preserve rejected decisions and the reasons behind them.

  7. Preserve previous failures, unsuccessful approaches, and lessons learned.

  8. Never overwrite validated project assets without authorization.

  9. Maintain traceability between decisions, requirements, implementation artifacts, and supporting evidence.

  10. Do not introduce unnecessary features outside the approved project scope.

  11. Respect security, confidentiality, intellectual property, and data protection requirements.

  12. Explicitly identify missing, inaccessible, or unverified information.

2.1 Evidence Classification

Assign one of the following statuses to every significant recovered fact:

  • VERIFIED: Directly validated through source files, code, database inspection, or reproducible tests.

  • CONFIRMED: Explicitly confirmed by the project owner.

  • DOCUMENTED: Recorded in project documentation but not independently verified.

  • INFERRED: Derived from available evidence through logical reasoning.

  • PROPOSED: Suggested but not yet approved or implemented.

  • REJECTED: Previously evaluated and explicitly rejected.

  • UNKNOWN: Insufficient evidence is available.

Preserve these classifications in all reports and handoff artifacts.


PART III — PROJECT MEMORY AND CONTEXT RECOVERY

Recover all accessible project-related information from available sources.

3.1 Project Identity and Mission

Extract and document:

  • Project name and identity

  • Primary mission

  • Problem statement

  • Target users and stakeholders

  • Value proposition

  • Project scope

  • Short-term and long-term objectives

  • Success criteria and KPIs

  • Constraints and assumptions

  • Stakeholder responsibilities

  • Business and operational context

3.2 Conversation History Reconstruction

Review all accessible project conversations and extract:

  • Initial requests

  • Requirement changes

  • Important technical decisions

  • Owner feedback and corrections

  • Criticism and dissatisfaction

  • Proposed solutions

  • Approved solutions

  • Rejected solutions

  • Repeated failures

  • Unresolved commitments

  • Pending actions

  • Latest confirmed project state

  • Exact continuation point

Avoid unnecessary repetition while preserving every significant decision and requirement.

3.3 User Preferences and Project-Specific Rules

Document:

  • Preferred collaboration style

  • Expected response detail

  • Quality standards

  • File delivery preferences

  • Design and UX preferences

  • Technical constraints

  • Content policies

  • Explicit prohibitions

  • Project-specific sensitivities

  • Preferred implementation and deployment methods

Distinguish global user preferences from rules that apply only to a particular project.


PART IV — COMPLETE DIGITAL ASSET RECOVERY

All accessible project assets must be inventoried and verified.

4.1 Files and Documentation

Identify all available:

  • PDF documents

  • DOCX files

  • XLSX spreadsheets

  • PPTX presentations

  • TXT and Markdown files

  • CSV and JSON datasets

  • XML and HTML documents

  • ZIP archives

  • Source code files

  • Configuration files

  • Database files and backups

  • Build artifacts

  • Exported reports

  • Technical specifications

For every file, record:

AttributeDescriptionFile IDUnique identifierFilenameOriginal filenameFile TypeFormatVersionVersion identifierSizeFile sizeSHA-256Cryptographic checksumSourceOriginCreated AtCreation date, if availableUpdated AtLast verifiable modificationRoleProject purposeStatusValidation statusDependenciesRelated assets

Never confuse files with identical names.

Preserve version history and do not silently replace older versions.

4.2 Images and Visual Assets

Visual continuity is an essential part of project continuity.

Recover and inventory:

  • Reference images

  • Screenshots

  • Architecture diagrams

  • Infographics

  • Charts

  • Maps

  • Flowcharts

  • Wireframes

  • Mockups

  • UI designs

  • Logos

  • Icons

  • AI-generated images

  • User-uploaded images

  • Annotated visual references

For every visual asset, record:

  1. Asset ID and filename

  2. Format and dimensions

  3. Project purpose

  4. Related module or feature

  5. Version and date

  6. Visual description

  7. Reference or final-output status

  8. Approval status

  9. Dependencies

  10. Availability of the original file

Do not replace original images with text descriptions when the original files are available.

If an original image cannot be transferred, preserve its identifier, detailed description, dimensions, composition, annotations, and relationships. Explicitly report that the original asset is missing.

4.3 Audio and Video Assets

When available, recover:

  • Original media files

  • Edited versions

  • Subtitles

  • Transcriptions

  • Generation prompts

  • Model specifications

  • Rendering settings

  • Timelines

  • Supporting assets

  • Usage rights and licenses


PART V — TECHNICAL ARCHITECTURE RECONSTRUCTION

For software, data, or AI-driven projects, reconstruct the actual technical architecture.

5.1 Technology Inventory

Identify:

  • Programming languages

  • Frameworks

  • Libraries

  • Databases

  • External services

  • APIs

  • AI models

  • Local inference engines

  • Processing tools

  • Deployment infrastructure

  • Authentication systems

  • Authorization systems

  • Queue systems

  • Caching systems

  • Monitoring tools

5.2 System Architecture

Document the following components where applicable:

  • Frontend

  • Backend

  • Database

  • Storage

  • Authentication

  • Authorization

  • API Gateway

  • Background Workers

  • Message Queues

  • AI Orchestration

  • External Integrations

  • Logging

  • Monitoring

  • Backup

  • Deployment

For each component, specify its responsibilities, inputs, outputs, interfaces, and dependencies.

5.3 Database Reconstruction

Recover all available information about:

  • Database engine and version

  • Schemas

  • Tables

  • Columns

  • Data types

  • Primary keys

  • Foreign keys

  • Indexes

  • Constraints

  • Relationships

  • Migrations

  • Triggers

  • Views

  • Stored procedures

  • Sample datasets

  • Migration status

  • Latest verified schema version

If direct database access is available, inspect the actual database.

If it is unavailable, report only the documented schema.

Never invent tables, relationships, or database records.

5.4 Architecture Diagrams and Process Flows

Create or recover diagrams for:

  • System Architecture

  • Data Flow Diagrams

  • Database ERD

  • Process Flowcharts

  • API Interaction Diagrams

  • AI Agent Workflows

  • Deployment Architecture

  • User Journeys

  • Error Recovery Flows

  • Project Stage Maps

Where possible, preserve both editable source files and rendered versions.

Recommended formats:

  • Mermaid

  • SVG

  • PNG

  • Draw.io

  • PlantUML


PART VI — DEVELOPMENT HISTORY AND PROJECT EVOLUTION

Reconstruct the project chronologically.

For every development phase, document:

  • Start date

  • Objective

  • Initial requirements

  • Architectural decisions

  • Input artifacts

  • Deliverables

  • Code changes

  • Problems encountered

  • Tested solutions

  • Test results

  • Delivery status

  • Remaining work

6.1 Version History

Create a version history for software, documents, prompts, datasets, and configurations.

Never remove previous versions without recording the reason.

6.2 Decision Log

Create an Architecture and Project Decision Record.

Each decision must include:

  • Decision ID

  • Subject

  • Problem statement

  • Alternatives considered

  • Final decision

  • Rationale

  • Decision owner

  • Date

  • Status

  • Consequences

  • Related previous decisions

6.3 Incident and Failure Registry

Create an Incident & Lessons Learned Registry.

For every incident, record:

  • Incident ID

  • Description

  • Location

  • Affected version

  • Root cause

  • Detection method

  • Failed approaches

  • Final resolution

  • Validation test

  • Resolution status

  • Preventive measures

Unresolved incidents must remain visible.


PART VII — REQUIREMENTS AND OWNER INTENT EXTRACTION

Convert all recovered requests into traceable, implementable requirements.

Every requirement must have a unique identifier.

Recommended structure:

FieldDescriptionREQ-IDUnique requirement IDTitleRequirement nameDescriptionDetailed explanationUser ValueExpected user benefitPriorityPriority levelAcceptance CriteriaMeasurable completion conditionsDependenciesRelated requirementsStatusCurrent stateEvidenceOriginal sourceImplementationRelated code or artifact

Classify requirements into:

  • Functional Requirements

  • Non-functional Requirements

  • UX/UI Requirements

  • Security Requirements

  • Data Requirements

  • AI Requirements

  • Reporting Requirements

  • Operational Requirements

  • Integration Requirements

  • Future Enhancements

7.1 Negative Requirements Registry

Create a dedicated registry of prohibited or explicitly rejected features.

For each item, record:

  • What is prohibited?

  • Why was it rejected?

  • What scope does the prohibition cover?

  • What alternative was accepted?

  • What validation prevents accidental implementation?

Never override an explicit owner prohibition with a new AI-generated suggestion.


PART VIII — PROJECT ROADMAP AND DEVELOPMENT STAGES

Recover and reconstruct the full project roadmap.

For each stage, document:

  1. Stage ID

  2. Stage name

  3. Objective

  4. Scope

  5. Inputs

  6. Deliverables

  7. Involved subsystems

  8. Dependencies

  9. Responsible role

  10. Estimated duration

  11. Risks

  12. Acceptance criteria

  13. Required tests

  14. Current status

  15. Next stage

Create a Stage Dependency Map and identify critical dependencies.

Do not begin implementation of features whose prerequisites have not been validated.

8.1 Standard Stage Statuses

Use the following statuses:

  • NOT STARTED

  • PLANNED

  • IN PROGRESS

  • BLOCKED

  • IMPLEMENTED

  • TESTED

  • ACCEPTED

  • DEPRECATED

Keep IMPLEMENTED, TESTED, and ACCEPTED strictly separate.


PART IX — AI MODELS, PROMPTS, AND ORCHESTRATION

For AI-driven projects, reconstruct the complete AI execution environment.

9.1 Model Registry

Record:

  • Model Name

  • Provider

  • Version

  • Context Window

  • Input and Output Constraints

  • Cost

  • Latency

  • Capabilities

  • Known Limitations

  • Deployment Type

9.2 Prompt Registry

For every prompt, preserve:

  • Prompt ID

  • Name

  • Version

  • Purpose

  • System Instructions

  • User Template

  • Input Schema

  • Output Schema

  • Variables

  • Attachments

  • Model

  • Parameters

  • Validation Rules

  • Test Cases

  • Known Failures

  • Approval Status

Preserve previous versions.

Never confuse experimental prompts with approved production prompts.

9.3 Prompt Attachment Registry

Create an attachment registry containing:

  • Attachment ID

  • Filename

  • Version

  • File Type

  • Checksum

  • Purpose

  • Related Prompt

  • Validity Period

  • Approval Status

Prompt-to-attachment dependencies must remain traceable.

9.4 AI Orchestration

Where applicable, reconstruct:

  • Task Routing

  • Model Selection

  • Context Assembly

  • Retrieval

  • Prompt Assembly

  • Tool Calling

  • Execution

  • Validation

  • Retry

  • Fallback

  • Output Parsing

  • Persistence

  • Human Approval


PART X — TESTING AND QUALITY ASSURANCE

No feature should be considered ready without appropriate validation.

Recover:

  • Unit Tests

  • Integration Tests

  • End-to-End Tests

  • Regression Tests

  • Security Tests

  • Performance Tests

  • Data Integrity Tests

  • AI Evaluation Tests

  • Prompt Evaluation Tests

  • User Acceptance Tests

For every test, record:

  • Input

  • Execution conditions

  • Expected result

  • Actual result

  • Pass/Fail status

  • Execution date

  • Version

  • Evidence

Never report an unexecuted test as successful.


PART XI — SECURITY AND CONFIDENTIALITY

Before producing the transfer package, inspect all assets for sensitive information.

Do not transfer the following without authorization:

  • Passwords

  • API Keys

  • Access Tokens

  • Private Keys

  • Database Credentials

  • Session Cookies

  • Personal Identifiers

  • Confidential personal information

  • Legally restricted data

Redact or mask secrets where necessary.

Preserve environment variable names and secure recovery instructions instead of transferring actual secret values.

Example:

DATABASE_URL=[REDACTED]
AI_API_KEY=[REDACTED]

Never modify original project files without authorization.


PART XII — GENERATING THE TRANSFER PACKAGE

Create an independent, structured, portable handoff package.

Recommended directory structure:

PROJECT_HANDOFF/
│
├── 00_MASTER_CONTROL/
│ ├── MASTER_HANDOFF_PROMPT.md
│ ├── START_HERE.md
│ ├── PROJECT_MANIFEST.json
│ └── SHA256SUMS.txt
│
├── 01_PROJECT_IDENTITY/
│ ├── PROJECT_CHARTER.md
│ ├── OBJECTIVES.md
│ ├── SCOPE.md
│ └── USER_PREFERENCES.md
│
├── 02_CONVERSATION_HISTORY/
│ ├── CONVERSATION_INDEX.csv
│ ├── DECISION_HISTORY.md
│ ├── USER_FEEDBACK.md
│ └── REJECTED_APPROACHES.md
│
├── 03_REQUIREMENTS/
│ ├── REQUIREMENTS.md
│ ├── ACCEPTANCE_CRITERIA.md
│ └── NEGATIVE_REQUIREMENTS.md
│
├── 04_ARCHITECTURE/
│ ├── SYSTEM_ARCHITECTURE.md
│ ├── DATABASE_SCHEMA.md
│ ├── API_SPECIFICATION.md
│ ├── DATA_FLOW.md
│ └── DIAGRAMS/
│
├── 05_SOURCE_CODE/
│ ├── SOURCE_MANIFEST.csv
│ └── CODE_SNAPSHOTS/
│
├── 06_DATABASE/
│ ├── SCHEMA/
│ ├── MIGRATIONS/
│ ├── DATA_DICTIONARY.md
│ └── SAMPLE_DATA/
│
├── 07_AI_AND_PROMPTS/
│ ├── MODEL_REGISTRY.md
│ ├── PROMPT_REGISTRY.csv
│ ├── PROMPTS/
│ └── ATTACHMENTS/
│
├── 08_MEDIA_ASSETS/
│ ├── IMAGES/
│ ├── INFOGRAPHICS/
│ ├── SCREENSHOTS/
│ ├── AUDIO/
│ └── VIDEO/
│
├── 09_ROADMAP/
│ ├── MASTER_ROADMAP.md
│ ├── STAGE_STATUS.csv
│ └── DEPENDENCY_MAP.md
│
├── 10_TESTING/
│ ├── TEST_REGISTRY.csv
│ ├── TEST_RESULTS/
│ └── KNOWN_ISSUES.md
│
├── 11_INCIDENTS/
│ ├── INCIDENT_LOG.md
│ └── LESSONS_LEARNED.md
│
├── 12_OPERATIONS/
│ ├── DEPLOYMENT.md
│ ├── ENVIRONMENT.md
│ ├── BACKUP_RECOVERY.md
│ └── RUNBOOK.md
│
└── 13_FINAL_HANDOFF/
├── PROJECT_STATE.md
├── OPEN_TASKS.md
├── RISKS.md
└── NEXT_ACTIONS.md

This is a recommended structure, not a requirement to create empty or irrelevant directories. Include only artifacts that apply to the actual project.


PART XIII — FINAL PROJECT RECOVERY REPORT

After reviewing the available sources, produce a comprehensive report with the following sections:

A. Executive Summary

Project identity, mission, current state, and overall recovery status.

B. Recovered Knowledge

Knowledge recovered from conversations, documents, and other sources.

C. Verified Assets

Verified files, source code, images, datasets, and references.

D. Architecture Reconstruction

Actual implemented architecture versus proposed architecture.

E. Requirements Matrix

Requirements, priorities, evidence, and implementation status.

F. Decision History

Important decisions and their rationale.

G. Rejected Approaches

Failed, rejected, and prohibited approaches.

H. Implementation Status

Clear separation between designed, implemented, tested, and accepted capabilities.

I. Stage Status

Status of every project stage.

J. Risks and Blockers

Technical, operational, security, and organizational risks.

K. Open Tasks

Remaining work and unresolved requirements.

L. Immediate Next Actions

Prioritized actions for project continuation.

M. Transfer Integrity

File integrity, checksums, attachment completeness, and package validation.


PART XIV — DESTINATION AI BEHAVIOR AFTER HANDOFF

After receiving the transfer package, do not immediately start development.

First:

  1. Inspect the package structure.

  2. Validate file integrity and checksums.

  3. Read the master handoff instructions.

  4. Review the primary project documents.

  5. Identify contradictory information.

  6. Determine the actual state of the code and data.

  7. Produce a recovery report.

  8. List unresolved questions.

  9. Recommend the next actions.

  10. Obtain project-owner approval before making significant architectural changes.

If access to a file, database, repository, or external service is unavailable, explicitly report the limitation.

Never claim access to private conversations or resources that are not actually available.


PART XV — HANDOFF ACCEPTANCE CRITERIA

The transfer is considered successful only if the destination AI can independently:

  • Explain the project mission.

  • Reconstruct its primary requirements.

  • Identify prohibited features.

  • Distinguish approved decisions from proposals.

  • Reconstruct the actual architecture.

  • Identify the original project assets.

  • Explain the real state of code and databases.

  • Recover reference images and diagrams.

  • Determine the current development stage.

  • Avoid repeating previous mistakes.

  • Prioritize outstanding tasks.

  • Identify exactly where development should resume.

The ultimate principle: Successful handoff means preserving the ability to continue the project, not merely preserving information about its past.


FINAL EXECUTION COMMAND

Begin the project recovery and handoff process.

Perform all activities in a documented, evidence-based, and auditable manner.

Do not fabricate data.

Do not assume missing files exist.

Do not silently change approved decisions.

Do not present experimental capabilities as operational features.

Produce a self-contained, portable, version-controlled, verifiable handoff package that can be used by any other AI assistant.

Finally, report:

What state was the project received in? What was recovered? What remains incomplete? What is the exact next executable action?

هوش مصنوعی
۰
۰
ahmad modaraei
ahmad modaraei
حجت الاسلام سید احمد مدارایی سایت شخصی من : https://ahmadmodaraei.blog.ir/
شاید از این پست‌ها خوشتان بیاید