0X03 Σ: ∃x:¬∃x (ENG)
From: elliot.groves@ire.org
To: 802.13@ire.org
Date: 1993-03-08 16:27:11 UTC
We've successfully completed baseline tests on the prototype-j L1/L1 transceiver provided by Argosy Advanced Systems under subcontract from the Department of Applied Research.
Results indicate a consistent reduction in signal latency, seemingly independent of cable length. Measured throughput exceeds 112 Mbps under sustained load.
All teams should continue utilizing the j-series bridge for further testing.
—
Elliot Groves
Lead Engineer, IRE 802.13 Working Group
From: k.misawa@ire.org
To: 802.13@ire.org
Date: 1993-04-17 21:04:02 UTC
Bidirectional flow testing with transceivers j04 and j05 confirmed stable transmission in both directions.
Synchronization between segments of unequal length was achieved without additional jitter.
Synchronization logs attached (see /mnt/80213/j-series/log_0417.misawa).
—
Kimi Misawa
Channel Synchronization
From: elliot.groves@ire.org
To: 802.13@ire.org
Date: 1993-06-12 11:18:35 UTC
Subject: Administrative Reclassification of Project 802.13 and Transfer of Oversight
This week, I received official notification that the 802.13 working group, in its current form, is subject to administrative wind-down and immediate transfer to external oversight under the SPECTRA initiative.
This decision stems from recent test results using j-series L1/L1 transceiver prototypes. The performance exceeded our initial technical expectations but attracted attention from authorities beyond our jurisdiction.
Accordingly, all operations, documentation, and further developments related to 802.13 hardware and protocols are transferred to an external agency. Individual staff will be contacted by SPECTRA representatives regarding potential transfers or additional clearances.
IRE will continue work related to Ethernet under the designation 802.3u (Fast Ethernet). Participants in this area will receive updated instructions and technical mandates in the coming weeks.
Personally, I want to thank all team members for your dedication, ingenuity, and professional integrity throughout this unique endeavor.
—
Elliot Groves
Lead Engineer, IRE 802.13 Working Group
From: spectra.intake@doar.gov
To: elliot.groves@ire.org
CC: registrar@spectra.gov, internal@ire.org
Date: 1993-06-14 06:42:01 UTC
Subject: Transfer of IRE 802.13 Working Group Under SPECTRA Oversight
In accordance with Directive 415.11 of the Department of Applied Research, Project 802.13 and associated materials now fall under restricted federal classification.
All original documentation, physical prototypes, signal logs, and component inventories must be handed over to designated SPECTRA representatives no later than June 19, 1993.
Personnel selected for clearance will receive individual notification from liaison officers.
Disclosure of transceiver design, signal behavior, or test results to unauthorized individuals will be considered a violation of Section 702(b) of the Federal Technical Secrecy Act.
This notice nullifies all previous mandates and agency-level permissions.
—
Office of Federal Integration
SPECTRA Directorate
Department of Applied Research
From: fed-enforcement@nti.gov
To: registrar@spectra.gov
Date: 1993-06-15 09:12:27 EST
Subject: Enforcement of Classification for 802.13 Derivatives
This is to inform you of escalated control over compliance with clearance protocols.
Effective June 16, 1993, any civilian or research institution possessing j-series-based equipment, signal sets, or derivatives must submit residual declarations and surrender forms in accordance with NTI Form 188-F.
Attempts to retain, analyze, or discuss signal characteristics identified within Project 802.13 will be considered violations of federal law.
SPECTRA is required to coordinate with NTI regional units to verify compliance.
—
Network Technology Integrity Control Office
Federal Technical Security Command
NTI.gov
From: richard.novak@ire.org
To: tom.chambers@ire.org
Date: 1993-06-17 22:49:58 UTC
Subject: (personal) I Won't Sign This Thing
I just received an NDA packet from the SPECTRA folks. I'm sure you did too.
This isn't a standard confidentiality agreement—it's a gag order.
Clause 3.4.2 states that I would be legally liable for "secondary dissemination effects caused by indirect disclosure of physical interface behavior." This is about physics, Tom. About a regular converter.
Another clause prohibits us from "reconstructing or describing the L1-to-jL1 connection"—even within IRE internal channels—for ten years.
I don't understand how we went from measuring signal latency to a complete shut-up-and-don't-breathe scenario. It's just a transceiver. Yes, incredibly efficient—beyond our expectations—but still just copper and logic.
I won't sign this. At least not until they explain why they're acting like we've uncovered some kind of combat protocol.
From: tom.chambers@ire.org
To: richard.novak@ire.org
Date: 1993-06-18 03:12:41 UTC
Subject: re: (personal) I Won't Sign This Thing
I read your letter. I understand your concerns, and you're right, generally speaking.
But—honestly—discussing this in emails is probably not the best idea.
I don't understand what's behind this either. I don't like the wording of the document, and I'm not thrilled about all these restrictions. But I advise against making decisions until you've spoken directly with their legal team.
If they want silence—they're already monitoring channels.
Don't give them a reason to escalate.
Excerpt from leaked document: SPECTRA NDA, June 1993, redacted
3.4.2 Responsibility for Latent Dissemination
The signatory accepts responsibility for any dissemination effects arising from indirect description, reimplementation, or analogous interpretation of signal interaction phenomena related to j-series prototypes.
3.5.1 Restriction on Terminological Description
The signatory agrees not to describe the dynamics of the L1-to-L1 interface for a minimum of ten (10) years, whether orally, in writing, or visually, if such description:
(a) exceeds the terminology of IRE 802.3u;
(b) demonstrates unexplained deterministic behavior within sub-millisecond transitions.
3.7.4 Clause on Unverifiable Determinism
Acknowledging the irregular reproducibility of signal coherence effects within the clock cycle, the signatory agrees not to characterize behavior as stochastic, deterministic, emergent, or externally modulated without written approval from SPECTRA's Analytical Division.
7.2 Disclosure of Cognitive Models
Personnel are prohibited from conveying subjective impressions, intuitive schemas, or heuristic interpretations of interface behavior without verification by SPECTRA's Behavioral Control Department. Use of terms like "predictable," "non-local," or "signal-aware" is strongly discouraged.
From: benjamin.holloway@spectra.gov
To: lead.80213@spectra.gov
Date: 1993-06-23 08:12:44 UTC
Subject: Critical Staffing Shortage
I urgently request reinforcement for the SPECTRA 802.13 engineering team.
Following the transfer from IRE, key specialists from the original group either did not receive clearance or refused to sign the NDA (Novak, possibly Misawa), and some (Chambers, Groves) remained at IRE for administrative reasons.
I am the only remaining protocol specialist from the original team, and I lack sufficient support to safely assess or replicate the j-series conditions.
We are critically understaffed in signal architecture and channel diagnostics. The j-series interface cannot be replicated solo, and continuing work under current conditions is unacceptable.
Frankly—this shouldn't be a "black box" project. We need personnel with clearance and experience with jL1.
—
Benjamin Holloway
Protocol Architecture, SPECTRA 802.13
From: lead.80213@spectra.gov
To: benjamin.holloway@spectra.gov
Date: 1993-12-05 15:47:31 UTC
Subject: Re: Critical Staffing Shortage
Understood. Forwarding the request to the Office of Special Infrastructure Oversight, attaching your memo.
You're right—the mismatch between task load and cleared personnel is unacceptable. Requesting specifically engineers with Level 4 clearance and proven Layer 1 experience.
Until reinforcements arrive, suspend all active j-series testing: no load, no alt-configs, no signal distortion experiments.
—
Dr. Alan Reed
Project Lead, SPECTRA 802.13
Board: internal://bbs.spectra.d4/net/sys_trace
Subject: [personal]/b-holloway/0420
Date: 1994-04-20 03:08:41 UTC
From: bholloway
To: tchambers
Subject: documents and inconsistencies
These "newcomers" they sent us — paperwork says they're RAND contractors on a temporary transfer. Names, codes, site assignments — everything checks out.
But my nephew works in RAND ops, has access to the personnel registry. I asked him to verify. Not a single one of those names exists. Not even as interns. He checked three times. Even asked around. Nothing.
That alone might be a database screw-up. But there's more. And it's weirder.
They don't seem to occupy space. I'm not talking mysticism — I mean literally. You walk by them — your brain just skims past. No footsteps. No ambient signal shifts. Not even a trace — zero.
They look canine. Probably. But generic. Like a placeholder model — no defined breed. Not dogs, not jackals, not anything specific — just "canine-like." And their body language doesn't match behavior. Tail up when nervous. Ears forward when they should be angry. One of them blinked during a power spike and said, "That shouldn't have reoriented." I never mentioned orientation.
I think we're not being told everything. And I think — neither are they.
Chambers:
Ever notice how the less we understood, the more locks they slapped on us?
Misawa:
It started right after j.3. Maybe earlier. When delays dropped below physics.
Novak:
I'm still not sure it was a mistake. Maybe the opposite.
Chambers:
Too many coincidences. And too many people vanished from the project. Even just administratively.
Misawa:
And Ben. He didn't change all at once. First few months he argued. Then — silence. Just took notes.
Novak:
Then he started to "understand," as he called it. But couldn't explain.
Chambers:
Someone was working with him. Not from our team. Those "canine" RAND types nobody saw before.
Misawa:
He started speaking strangely. Like he wasn't talking about tech. Like it was structure. Or form. But not the form of a signal.
Novak:
I'm going to rebuild the testbed. Not the whole thing. Just the base topology. Without their transceivers.
Chambers:
You want to check it?
Novak:
I want to understand. What exactly went wrong. Or maybe — too right.
Misawa:
If you repeat it — don't connect it to an external network.
Novak:
I'm not. Just a loop. Closed environment only.
Chambers:
Tell us if you hear… anything.
Novak:
I'll tell you if I see something.
Subject: CHAMBERS, T. (T. Chambers)
Date: 1999-02-13
Location: [REDACTED]
Conducted by: AGENT [REDACTED], ID 417-C
Session Number: 1/1
Classification: INTERNAL EYES ONLY
417-C:
You state that after the dissolution of the 802.13 working group, you had no access to project-related equipment?
Chambers:
Yes. I was not transferred to SPECTRA. I moved to the private sector. I had no clearance. And if you check the paperwork, it wasn’t even offered.
417-C:
Did you maintain contact with other group members?
Chambers:
Sometimes. For a while.
417-C:
With whom, specifically?
Chambers:
Novak. And Misawa. Off and on. Outside work. Bars. Old times.
417-C:
When did you last speak to Novak?
Chambers:
In person — October ‘98. By phone — a week before the publication. Nothing after that. Calls stopped connecting.
417-C:
Did you read his material?
Chambers:
Yes. Before it disappeared. He posted a PDF on his personal server, mirrored it through a student host in Germany. It was gone within two hours. Even Google Cache was wiped.
417-C:
What was he trying to prove?
Chambers:
That there was no fault in the j-series interfaces. That we had inadvertently reproduced a stable phase emission usable for ultrafast sync without a reference clock. He called it “coherent spike.”
Chambers:
No. In the last section he wrote that the loopback transmission patterns started to reflect structure — not in the code, but in the board’s topology. As if the hardware itself decided what and when to transmit.
417-C:
You believe that’s possible?
Chambers:
I’m no science fiction engineer. But I saw us get a handshake on j.3 before any transmission began. That’s not supposed to happen.
Chambers:
I don’t know. She went to Osaka, then Singapore. Now — no one knows. Mail undeliverable. Calls drop.
417-C:
You’re aware that after Novak’s publication, there were attempts to replicate his experiment?
Chambers:
I didn’t participate.
417-C:
But you knew it was happening?
Chambers:
You’re repeating questions I’ve already answered.
417-C:
I’ll ask as many times as needed. We have confirmed attempts to transfer j-series schematics to Europe via private channels. Were you aware?
Chambers:
What agency did you say you’re with?
Chambers:
Is this an interrogation or just a conversation?
417-C:
We’re just documenting facts.
Chambers:
Alright. Then I’ll call my attorney. And we continue only in his presence.
Server: secmon.infra.gov
Channel: #review-queue
Date: 2004-06-12 19:23 UTC
Participants: @nora-y, @josh-c
<@nora-y>
I’ve got Chambers, Thomas G., born ‘57, outbound via JFK, purpose listed as “technical contract / staff training,” destination country — Ruthenia, host — MosTeleCore Systems.
<@nora-y>
Ex-engineer. Was in some international IRE group back in the 90s. Been retired for a while. Just a techie.
<@josh-c>
Then why’s he in our system?
<@nora-y>
That’s the weird part: he’s flagged with limit foreign access, Tier 2 tag, source: closed registry, something like S-OVR. No details.
<@josh-c>
Does limit foreign access mean “don’t let out”? Or “let out but notify local assets”? I can’t find a clear definition.
<@nora-y>
Asked Alex from Section 2 — says it’s an old tag, could mean anything. Sometimes just “no hardware abroad,” sometimes “notify consulate.”
<@josh-c>
Great. We let him out, and next thing he’s giving lectures on “the old days,” and it all goes sideways again.
<@nora-y>
Technically, there’s no grounds to stop him. No current federal work, no clearance, no charges.
I’ve flagged him to embassy systems. If anything weird happens, they’ll log it.
<@josh-c>
Is he even lucid? 1957 birth year. Or maybe it’s just technoromantics. “Last engineer of the analog era.”
<@nora-y>
Or maybe not just that.
Memo
Federal Migration Service, Ruthenia / Domodedovo Airport (DME)
Ref. No: 14-99/VX-191
Dated: June 14, 2004
ON CONFIRMED NON-ARRIVAL OF FOREIGN NATIONAL ON ROUTE LHR–DME
During scheduled verification of foreign arrivals at the state border checkpoint, Domodedovo Airport, flight Transaero UN456 (London – Moscow), June 13, 2004, the following was established:
U.S. citizen Chambers Thomas George, born 1957, U.S. Passport No. 300174828, was cleared for entry to the Federation of Ruthenia under contract with MosTeleCore Systems (visa type: short-term business, RU-DV-4417/04).
His name appeared in the pre-flight manifest registered in the ETL system for flight UN456, June 13, 2004 — seat 34F.
British Airways staff at Heathrow (Terminal 4) confirmed that the boarding pass was presented, ID verified, and boarding granted.
However, there is no visual record of the subject in the jetway, holding area, or gate boarding footage.
The DME “Rubezh” border control system has no record of the subject crossing.
Flight crew questioned post-arrival could not confirm the passenger’s presence with certainty. Cabin staff in economy sections 3 and 4 were instructed to log “no incidents; seat was occupied or not noticed.”
Baggage registered to CHAMBERS T.G. arrived, was offloaded, and is now in unclaimed storage (tag DME/13/06/NV172).
A re-exported electronic manifest (dated 14.06.2004, 06:00 MSK) omits the name CHAMBERS from the flight list. A printed copy from 13.06.2004, 15:10 UTC is archived at DME.
- cleared boarding at Heathrow;
- appeared in original digital and physical manifests;
- was not visually confirmed boarding;
- did not arrive at Ruthenia border control;
- did not claim baggage.
- Assign “Boarded – Not Arrived (BNA)” status and log entry in Migration Trace DB;
- Issue notification to Ministry of Foreign Cooperation and U.S. Consular Service in Moscow;
- Request Heathrow (T4) surveillance archives for 13.06.2004, 16:40–18:20 UTC, sector UN456 boarding, for biometric trace analysis;
- Report manifest mismatch to Transaero Security, request source confirmation for manifest edit;
- If further info arises — escalate to H-II / Tier-2 trace (archived flag).
Filed by:
Senior Inspector, FMS Ruthenia / DME Sector
M.A. Zimin
[signature, stamp]
IRE/INT-PRO/802.13
Date: 2007-02-11
Type: Final Notice
To: IRE Central Archive (TechComm)
CC: SPECTRA Division / DAR
From: Protocol Coherence Office
Re: Project 802.13 (j-revision) Final Consolidation
Pursuant to internal commission decisions of 23.01.2007, protocol 802.13-j (FastLink Interoperability Draft) will not be transitioned to public release.
The unified vendor registry (2004–2006) has been archived. Unapproved alterations by third parties were excluded from technical records. Final version matrix (ref: 13j_consensus.xls) is filed as a historical record of an alternative L1 transceiver development attempt that did not continue.
Reconnections logged in certain regions post-testing were classified as unidentified local configurations and do not affect protocol status.
“j” and “pre-j” branch distinctions are deprecated. Instance IDs are removed from the active project base. All logs, including error and interim, are available offline upon request (ref: TapeSet 17-B, D/SEG-Δ storage).
No further action required by IRE.
802.13-j registry closed. Segment removed from network mapping model.
Signed:
E. Carter
Acting Senior Coordinator, Archival Standards
Note:
Project 802.13 remains non-citable. Terminology requests must be routed to DAR/SPECTRA prefilter office.