Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,14 @@ ApexCode is an independent open-source engineering control-plane project built o

**Status:** bootstrap / experimental. ApexCode is not an official OpenAI product and is not endorsed by OpenAI.

## ApexCode Status

- **Safety Kernel v0.1** — [security-reviewed candidate](./docs/APEXCODE-SAFETY-KERNEL-V0.1.md)
- **Runtime Adapter v0.1** — [first real Codex pre-execution policy gate](./docs/APEXCODE-RUNTIME-ADAPTER-V0.1.md)

These documents describe reviewed experimental candidates; they do not claim
production readiness or official OpenAI endorsement.

The project focuses on capabilities around Codex rather than replacing its core unnecessarily:

- persistent long-horizon task state
Expand Down
67 changes: 67 additions & 0 deletions docs/APEXCODE-RUNTIME-ADAPTER-V0.1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
# ApexCode Runtime Adapter v0.1

Status: security-reviewed candidate. This document describes the first
reviewed runtime integration; it is not a production-readiness claim.

## Reviewed candidate

Exact reviewed SHA:

`3575971d7be163413a1abe9be71224b8d332e012`

Runtime boundary:

`codex-rs/app-server/src/message_processor.rs`
`MessageProcessor::handle_initialized_client_request`

Gated action:

`ClientRequest::FsReadFile` / `fs/readFile`

## Architecture

```text
Codex Request
↓
Apex Runtime Adapter
↓
Risk Classification
↓
Apex Policy
↓
ALLOW / BLOCK / DENY
↓
Existing Codex execution
```

The gate runs **before** `FsRequestProcessor::read_file`. A blocked request
returns without invoking the existing filesystem processor. An allowed request
then continues to the existing Codex implementation.

ApexCode does not replace the existing Codex filesystem implementation. The
adapter is an opt-in compile-time feature and does not create evidence,
approval, trusted execution receipts, or release authority. It is disabled in
the normal app-server build to preserve intentional upstream compatibility.

## Public validation results

- Safety kernel: **70/70 PASS**
- Runtime adapter: **10/10 PASS**
- Focused upstream integration: **3/3 PASS**
- Nearest upstream filesystem regression: **14/14 PASS**
- Security review: **HIGH 0, MEDIUM 0, LOW 0**
- Kernel modification: **NONE**
- Alternate `fs/readFile` bypass: **ABSENT**
- Blocked request invokes the filesystem processor: **NO**
- Adapter-disabled compatibility: **PASS**

The integration remains a reviewed candidate and is not claimed to be
production-ready.

## Project positioning and provenance

ApexCode is an independent open-source project based on [OpenAI
Codex](https://github.com/openai/codex). It is not an official OpenAI product
and is not endorsed by OpenAI. Apache-2.0 attribution and upstream provenance
are preserved; see the repository [LICENSE](../LICENSE), [NOTICE](../NOTICE),
and [UPSTREAM.md](../UPSTREAM.md).
59 changes: 59 additions & 0 deletions docs/APEXCODE-SAFETY-KERNEL-V0.1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,59 @@
# ApexCode Safety Kernel v0.1

Status: security-reviewed candidate. This document describes the reviewed
foundation; it is not a production-readiness claim.

## Reviewed foundation

Safety Kernel SHA:

`bae1efc121a158c91cab08b8ae4e7cfe4199e77f`

The kernel is composed of:

- `apex-policy`
- `apex-task-state`
- `apex-evidence`
- `apex-orchestrator`
- `apex-runtime-trust`

## Evidence

- Kernel test suite: **70/70 PASS**
- Eight previously discovered security findings were remediated and
revalidated.

The reviewed kernel provides these security properties:

- unknown classifications fail closed;
- evidence is bound to the exact task, revision, and source;
- stale evidence is invalidated;
- implementation, review, security, and release roles remain separated;
- task checkpoints are authenticated;
- source provenance is verified;
- arbitrary command execution produces non-authoritative observations;
- runtime decisions protect against stale time-of-check/time-of-use state;
- R4 release requires explicit release authority; and
- R5 is denied by default.

## Engineering context

ApexCode grew out of real-world Codex use across 11 GPRO projects. That
experience covered AI orchestration, Laravel and business applications,
realtime support, publishing, SEO and workflow automation, infrastructure and
DevOps, security, and multi-repository operations. No proprietary source is
included in this description.

Repeated operational experience motivated persistent task state,
evidence-bound completion, role separation, runtime provenance, fail-closed
execution, and policy gates.

## Project positioning and provenance

ApexCode is an independent open-source project based on [OpenAI
Codex](https://github.com/openai/codex). It is not an official OpenAI product
and is not endorsed by OpenAI.

The project preserves Apache-2.0 attribution and upstream provenance. See the
repository [LICENSE](../LICENSE), [NOTICE](../NOTICE), and
[UPSTREAM.md](../UPSTREAM.md).