◈05The intake valve

The Publisher

A narrow, server-side way for ChatGPT to create a GitHub Issue in hopchouinard/cognitive-backlog. It validates hard, writes only to the one configured repository, and keeps GitHub credentials away from ChatGPT.

Stunningly basic security, which is exactly what we want.

— docs/chatgpt-publisher.md

Runtime surface

GET/healthliveness
GET/.well-known/oauth-protected-resourceOAuth resource metadata
POST/mcpChatGPT App / MCP tool (OAuth-protected)
POST/publish_to_cognitive_backlogCustom GPT Action fallback (shared secret)

Anatomy of a capability

Edit the payload. Watch the derived labels and the exact GitHub issue body update live — using the same rules the real publisher documents. Type an implementation task and it gets rejected, because this repo stores capabilities, not chores.

✓ Reads like a capability. This describes an ability, not a chore.

Domain
Suggested runtime

Derived labels

P2Mstrategyplanningloopideasource:chatgpt

GitHub issue body

# Cognitive Capability

## Objective

Produce a weekly synthesis of what changed and what deserves attention next.

## Motivation

Long-horizon thinking decays without a recurring forcing function.

## Expected Outcome

A concise weekly brief highlighting progress, risks, and next moves.

## Candidate Inputs

- backlog changes
- production status
- recent decisions

## Candidate Outputs

- weekly brief
- recommended focus list

## Success Description

The brief consistently surfaces the few things that matter.

## Priority

P2

## Complexity

M

## Domain

- strategy
- planning

## Suggested Runtime

- loop

## Cognitive Value

4

## Origin

ChatGPT conversation

## Conversation Summary

Discussed keeping long-horizon priorities from drifting.

## Related Capabilities

None

## Notes

Keep it short.

## Status

Idea