Skip to content

Code organization policy should require alerting human on codebase conflicts #10

@wtmoose

Description

@wtmoose

Friction

A code organization policy specifies // MARK: - <ProtocolName> for protocol conformance implementations. The entire codebase (90+ files) used a different convention. When writing a new file, the LLM initially followed the policy, then silently reverted to match the codebase pattern without flagging the conflict. The correct action would have been to alert the human that existing code conflicts with the policy and ask for direction.

Suggestion

Add an enforcement rule to the code organization policy: when existing code patterns conflict with the policy, the LLM must stop, describe the conflict, and ask the human for direction rather than silently adopting either convention.

Affected files

Policies/swift-code-organization.md — Enforcement rules section.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions