Skip to content

YujunZhou/tellonce / codex

tellonce

Verified

Use to view, explain, correct, delete or reorganize the user's saved preferences, or to record one by hand when automatic recording is off; learning and rule injection otherwise run automatically through Codex hooks.

FileKindSize
.codex-plugin/plugin.jsonconfig1.3 KB
SKILL.mdskill md12.0 KB
dashboard.shexecutablescript348 B
docs/CC_PARITY_MATRIX.mdmarkdown7.3 KB
docs/README.mdmarkdown3.4 KB
doctor.shexecutablescript345 B
hooks/hooks.jsonconfig714 B
hooks/posttooluse-deterministic-block.shexecutablescript2.0 KB
hooks/sessionstart-init.shexecutablescript1.9 KB
hooks/userpromptsubmit-dispatch.pyscript2.6 KB
hooks/userpromptsubmit-memory-upsert.shscript326 B
hooks/userpromptsubmit-pending-inject.shexecutablescript2.0 KB
hooks/userpromptsubmit-retrieve-inject.shexecutablescript3.1 KB
hooks/userpromptsubmit-shadow-alert-inject.shexecutablescript1.2 KB
install.shexecutablescript13.9 KB
shared_lib/_install_merge_settings.pyscript12.1 KB
shared_lib/_pt_hooks.txtmarkdown407 B
shared_lib/correction_interpretation.pyscript8.5 KB
shared_lib/detect_user_prefer.pyscript7.2 KB
shared_lib/deterministic_block.pyscript9.3 KB
shared_lib/event_obligations.pyscript19.8 KB
shared_lib/execution_support.pyscript75.8 KB
shared_lib/fingerprints.yamlconfig1.1 KB
shared_lib/learning_policy.pyscript4.6 KB
shared_lib/memory_judge.pyscript84.8 KB
shared_lib/memory_publication.pyscript14.9 KB
shared_lib/memory_runtime.pyscript12.2 KB
shared_lib/memory_store.pyscript99.6 KB
shared_lib/memory_upsert.pyscript57.1 KB
shared_lib/memory_upsert_hook.pyscript4.6 KB
shared_lib/model_requests.pyscript5.8 KB
shared_lib/path_config.pyscript13.3 KB
shared_lib/pending_queue_manager.pyscript23.4 KB
shared_lib/pt_platform.pyscript1.5 KB
shared_lib/redaction.pyscript3.4 KB
shared_lib/retrieve_inject.pyexecutablescript57.9 KB
shared_lib/rule_selection.pyscript18.9 KB
shared_lib/shadow_alert_inject.pyscript6.1 KB
shared_lib/training_memory.pyscript17.8 KB
shared_lib/transcript_adapter.pyscript13.7 KB
shared_lib/verify_compliance.pyexecutablescript24.5 KB
shared_lib/verify_retry_shadow.pyscript27.4 KB
tellonce_codex/__init__.pyscript52 B
tellonce_codex/__main__.pyscript49 B
tellonce_codex/cli.pyscript6.8 KB
tellonce_codex/codex_posttooluse_block.pyscript11.2 KB
tellonce_codex/dashboard.pyscript3.4 KB
tellonce_codex/doctor.pyscript10.9 KB
tellonce_codex/index.pyscript1.8 KB
tellonce_codex/install.pyscript3.1 KB
tellonce_codex/install_codex_hooks.pyscript15.1 KB
tellonce_codex/ledger.pyscript17.1 KB
tellonce_codex/memory.pyscript5.3 KB
tellonce_codex/migrate.pyscript1.3 KB
tellonce_codex/mode.pyscript2.3 KB
tellonce_codex/paths.pyscript8.6 KB
tellonce_codex/promote.pyscript4.4 KB
tellonce_codex/scan.pyscript2.6 KB
tellonce_codex/uninstall.pyscript1.7 KB
tellonce_codex/verify.pyscript5.3 KB
tellonce_codex/wrapper.pyscript12.0 KB
uninstall.shexecutablescript4.6 KB

shared_lib/learning_policy.py

View on GitHub
"""Explicit learning scope for new experimental libraries and legacy libraries."""
GENERAL = 'general'
CORRECTIONS = 'corrections'
CORRECTION_TYPES = frozenset({'preference', 'friction', 'pitfall'})


def admission_instruction(policy: str) -> str:
    if policy == GENERAL:
        return ('Persist only durable preferences, recurring pitfalls, friction, user facts, '
                'project facts, or reusable references. A one-task instruction is not memory.')
    if policy != CORRECTIONS:
        raise ValueError('unknown learning policy')
    return (
        'Persist only reusable preferences, friction, or pitfalls expressed by the user. '
        'A correction can qualify without an explicit request to remember it. '
        'Apply this distinction BEFORE rejecting a message as task-specific: '
        '(1) a new requested choice or unexplained replacement is ordinary task work; '
        '(2) an explained correction identifies what went wrong in the assistant\'s '
        'process and can support that specific reusable pitfall even after ONE example. '
        'A sentence saying the chosen item fails the requested criteria, omits a '
        'required part, or lacks the stated evidence is not merely a new choice. '
        'Preserve its supported lesson without requiring "always", repetition, '
        'or a separate future-facing sentence. Reject it only if no behavior can '
        'be generalized without adding a requirement not expressed by the user. '
        'Distinguish a one-off choice from a correction that identifies a repeatable error: '
        'a concrete example does not make the underlying pitfall one-off. '
        'For example, "that selection is outside the range I gave; check the range" '
        'can support checking selections against the requested ranges, but not storing '
        'the example selection or treating that range as a standing preference. '
        'Extract only the reusable behavior directly supported by the correction; '
        'do not invent a cause, mandatory tool, extra verification step, or broader ban. '
        'Preserve the kind of claim and corrected relationship while removing incidental '
        'names. In particular, source-attribution fidelity is not a demand that all '
        'deductions, calculations or paraphrases occur verbatim in source text. '
        'Require exact words for direct quotations, and semantic support for paraphrases; '
        'do not apply the quotation standard to every attributed claim. '
        'Verifying a claimed source type is not requiring universally generalizable evidence. '
        'A bare replacement ("use B instead of A"), a new task requirement, or an '
        'explicit one-time exception does not by itself establish a reusable rule. '
        'Do not store task answers, specific factual knowledge, project facts, or reference material. '
        'This applies to the entire record, including body and description: keep '
        'concrete example names, dates, answers and incidental values only in the '
        'source evidence spans, not in the reusable rule record. '
        'Use record.type preference, friction, or pitfall only. '
        'Keep parameters, paths, tool names and thresholds only when they are part '
        'of the actual durable requirement, not an incidental failed example; '
        'generalization must not erase these or invent broader obligations. '
        'For an admitted reusable preference, do not append "if requested" or '
        '"when explicitly asked again" just because this correction is a request. '
        'The future trigger is the supported activity or object, not repetition '
        'of the correction. Preserve a genuinely stated opt-in condition or '
        'one-time limit; do not turn "only when I ask for X" into a default. '
        'If durability is unsupported, save no rule instead of a vacuous promise '
        'to comply only after the same request is repeated. '
        'A new one-task instruction is not memory; an explained error correction '
        'must still be assessed for a reusable pitfall as described above.'
    )


def validate_types(plan: dict, policy: str) -> None:
    admission_instruction(policy)
    if policy == GENERAL:
        return
    def visit(items):
        for item in items:
            if item.get('operation', '').upper() in {'NEW', 'UPDATE', 'SUPERSEDE'}:
                if item.get('record', {}).get('type') not in CORRECTION_TYPES:
                    raise ValueError('experimental memory accepts only preference, friction, or pitfall')
            visit(item.get('children') or [])
    visit(plan.get('mutations') or [])
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall