Skip to content

Define CLAUDE.md editing conventions and guidelines #17

Description

@mwiesen

These are open questions that should be answered and added to CLAUDE.md as clear rules for Claude Code.

Open questions

Editing conventions

  • Which version should be edited — always the working draft (v0.4), never the released (v0.3)?
  • Is released text considered frozen?

Writing style

  • Is the spec written in RFC-style formal prose?
  • Are there structural conventions per section (e.g. must every endpoint section have a JSON example, an error table, a security note)?

CR lifecycle

  • When does a Change Request get incorporated into the spec?
  • Should Claude treat CRs as authoritative proposals to implement, or just as ideas under discussion?

Cross-spec consistency

  • When a Core protocol change affects key exchange or connection handling, which specific sections in PME/SPE need to be updated?

Scope guardrails for Claude

  • What should Claude not do autonomously? (e.g. restructure sections, merge a CR into the spec without being explicitly asked)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions