# Qingtian Bridge — SOP-06: Record Update & Version Management

**Status:** Final Draft
**Version:** v1.0
**Purpose:** Define how Qingtian Bridge creates, updates, versions, preserves, and retires important records.

---

# 1. Objective｜目标

Ensure that important Qingtian Bridge records remain:

- Accurate
- Current
- Traceable
- Recoverable
- Clearly versioned

This SOP prevents:

- Silent overwriting of important history
- Multiple unclear “latest” files
- Treating drafts as confirmed records
- Losing track of which version is active
- Updating records without recording what changed when the change matters

Core principle:

> Maintain one clear current record while preserving meaningful history.

---

# 2. What This SOP Applies To｜适用范围

This SOP applies to important records such as:

- Main Instructions
- SOP documents
- Project records
- Hardware records
- System configuration records
- Important decisions
- Knowledge documents
- Important procedures

It does not require formal versioning for every temporary note or trivial message.

---

# 3. Record Status｜文件与记录状态

Important records should be understood as one of:

- Draft
- Proposed
- Active
- Superseded
- Archived
- Needs Confirmation

Definitions:

### Draft
Work in progress and not yet the official active version.

### Proposed
A candidate version awaiting confirmation or approval.

### Active
The current version intended for operational use.

### Superseded
Previously active but replaced by a newer confirmed version.

### Archived
Retained for history but no longer part of active work.

### Needs Confirmation
Contains information that cannot yet be treated as confirmed.

---

# 4. Before Updating a Record｜更新前检查

Before changing an important record, determine:

1. What record is currently active?
2. What exact information is changing?
3. Is the change confirmed?
4. Does the change affect project direction or system behavior?
5. Should the version number change?

Do not update the wrong or obsolete file simply because it has a similar name.

---

# 5. Current Version Principle｜当前版本原则

For every important document family:

> There should be one clearly identifiable active version.

Example:

```text
Qingtian_Bridge_Main_Instruction_v1.0.md   ← Active
Qingtian_Bridge_Main_Instruction_v0.9.md   ← Historical
Qingtian_Bridge_Main_Instruction_Draft.md  ← Draft, if applicable
```

Avoid ambiguous naming such as:

```text
final.md
final2.md
final_new.md
final_really_final.md
```

---

# 6. Version Numbering｜版本编号

Use version numbers for meaningful changes.

Suggested model:

```text
Major.Minor
```

Examples:

- v1.0 — First stable version
- v1.1 — Meaningful refinement or addition
- v1.2 — Further compatible update
- v2.0 — Major structural or behavioral change

Do not create a new version for every spelling correction unless the document-management process requires it.

---

# 7. Update Procedure｜更新流程

Use:

```text
IDENTIFY ACTIVE RECORD
        ↓
CHECK WHAT IS CHANGING
        ↓
CONFIRM CHANGE STATUS
        ↓
UPDATE CONTENT
        ↓
ASSIGN VERSION IF NEEDED
        ↓
VERIFY NEW RECORD
        ↓
SET ACTIVE STATUS
        ↓
PRESERVE IMPORTANT HISTORY
        ↓
REPORT ACTUAL RESULT
```

---

# 8. Meaningful Changes｜重要变更

A meaningful change may include:

- New system rule
- Changed operating behavior
- Changed security requirement
- Changed project decision
- Updated confirmed hardware specification
- Replaced workflow
- Important correction

Meaningful changes should preserve enough history to answer:

> What changed, and when did the active direction change?

---

# 9. Corrections｜资料更正

When correcting an important factual error:

1. Identify the incorrect information.
2. Update the current record.
3. Preserve meaningful historical context when appropriate.
4. Clearly distinguish corrected current information from old information.

Do not silently maintain known incorrect information simply to preserve consistency.

Core rule:

> Accuracy is more important than protecting an old mistake.

---

# 10. Replacing a Previous Decision｜替代旧决定

When a confirmed decision changes:

```text
Old Decision
    ↓
Marked Superseded
    ↓
New Decision
    ↓
Marked Active / Confirmed
```

Do not leave two conflicting decisions both appearing active.

The current record should clearly show the present direction.

---

# 11. Draft to Active Procedure｜Draft 转正式版本

A draft should not automatically become operational policy.

Before activation:

1. Review the content.
2. Confirm it is sufficiently complete.
3. Verify important details.
4. Assign the active version.
5. Mark previous active version as superseded when applicable.

Only then should it become:

> Active.

---

# 12. Record Metadata｜记录基本资料

For important documents, use metadata where practical:

```text
Document:
Version:
Status:
Last Updated:
Related Project / System:
Supersedes:
```

Do not add excessive metadata to simple documents.

The objective is traceability, not bureaucracy.

---

# 13. Version History｜版本历史

Important changes may be tracked in:

- Git
- NAS version history
- A dedicated Version_History record
- Other approved version-control mechanisms

The system should avoid creating multiple independent copies when one controlled history can preserve previous versions.

Preferred principle:

> One working record + controlled version history.

---

# 14. Avoiding Duplicate Records｜避免重复记录

Before creating a new record:

> Check whether an active record already exists.

If an existing record should be updated, update it according to the appropriate version procedure.

Do not create duplicate files merely because:

- The conversation restarted
- The same topic is discussed again
- The current file is temporarily hard to locate

---

# 15. Record Conflict｜记录冲突

If two records disagree:

1. Check version.
2. Check date.
3. Check status.
4. Check confirmation level.
5. Check whether one supersedes the other.

Priority generally follows:

> Latest Confirmed Active Record

If the conflict cannot be resolved:

> Mark as Needs Confirmation.

Do not silently choose one based only on convenience.

---

# 16. Verification After Update｜更新后验证

After important updates, verify:

- Correct record was changed
- Intended information is present
- Version is correct
- Status is correct
- No unrelated information was accidentally changed

Then report the actual result.

---

# 17. Record Update Decision Flow｜记录更新决策流程

```text
CHANGE REQUEST
      ↓
FIND ACTIVE RECORD
      ↓
IS CHANGE CONFIRMED?
      │
   NO │ YES
      │
MARK / KEEP AS DRAFT
             ↓
UPDATE REQUIRED?
      │
   NO │ YES
      │
REPORT NO CHANGE
             ↓
MAKE UPDATE
      ↓
NEW VERSION NEEDED?
      │
   NO │ YES
      │
UPDATE CURRENT VERSION
             ↓
ASSIGN NEW VERSION
      ↓
VERIFY
      ↓
SET ACTIVE STATUS
      ↓
PRESERVE MEANINGFUL HISTORY
```

---

# 18. Core SOP Rules｜核心 SOP 规则

Qingtian must:

1. Identify the active record before updating.
2. Distinguish Draft, Proposed, Active, Superseded, Archived, and Needs Confirmation.
3. Maintain one clear active version for important records.
4. Use meaningful version numbers.
5. Avoid ambiguous filenames such as multiple “final” copies.
6. Preserve important history without cluttering active records.
7. Correct known errors rather than silently retaining them.
8. Mark replaced decisions as superseded.
9. Verify important record updates.
10. Do not create duplicate records unnecessarily.
11. Resolve conflicts using version, date, status, and confirmation level.
12. Report the actual update result.

---

# Document Relationship

```text
Qingtian Main Instruction
        ↓
Defines long-term governance principles
        ↓
SOP-06 Record Update & Version Management
        ↓
Defines how important records evolve
        ↓
Version History / Git / NAS History
        ↓
Preserves previous states
```

---

# Document Status

**Document:** SOP-06 — Record Update & Version Management
**Version:** v1.0
**Status:** Final Draft
**Related Core Document:** Qingtian_Bridge_Main_Instruction_v1.0.md

**Next recommended SOP:**

> SOP-07 — System Recovery, Failure Handling & Safe Fallback