Is the past still “real” in a physical sense, or is its existence dependent on observation? (Time, determinism, philosophy of physics)

Hi everyone,

I’ve been thinking about a question regarding the nature of time that seems to sit somewhere between philosophy of physics and metaphysics, and I’d appreciate some guidance on how this is treated in existing literature.

A common way of speaking about time is to say that the past “no longer exists.” However, I’m wondering whether this reflects an ontological claim, or simply a limitation of human cognition (i.e., our inability to access or reconstruct past states of the universe).

More specifically, suppose we consider a view where every event that occurs leaves a permanent imprint in the structure of reality, even if that imprint becomes physically inaccessible or indistinguishable over time. This seems loosely compatible with physical principles like conservation laws, where nothing is truly lost but rather transformed.

This leads me to a few related philosophical questions:

  1. Ontological status of the past: In contemporary philosophy of time (e.g., presentism vs. eternalism), is there a position that treats past events as still “physically real” even if no observable traces remain? Or does most philosophical work tie existence to observability or causal accessibility?

  2. Epistemic vs. ontological limits: To what extent do philosophers distinguish between the past not existing and the past being in principle inaccessible? Are there frameworks that explicitly address this distinction?

  3. Determinism and the openness of the future: If the past is fixed and irreversible, but the future is described probabilistically (as in some interpretations of physics), how is the boundary between determinism and free will typically understood in philosophy? Is this tension addressed differently depending on one’s interpretation of time?

  4. Perception of time: Is the human experience of being “trapped in the present” generally treated as an evolutionary/psychological feature, or as something that has deeper philosophical implications for how we model reality?

If there are specific philosophers, theories, or papers (e.g., on eternalism, the block universe, or the arrow of time) that directly engage with these issues, I’d really appreciate references.

Thanks in advance

reddit.com
u/zetario13 — 13 days ago
▲ 8 r/agenticAI+5 crossposts

Aeris — deterministic ECS engine in C# (.NET 10) for cognitive simulation and narrative pipeline (technical analysis and review search)

Looking for technical feedback on Aeris — a deterministic cognitive simulation engine

Hi everyone.

I've been working on an open source project called Aeris, and I'd really appreciate technical feedback from people interested in simulation, AI architecture, ECS, or cognitive systems.

Repository:
https://github.com/Cedrick-Coto/Aeris

I didn't start this project because I wanted to build "another AI."

I started it because I've always been fascinated by AI in video games, but most NPCs never felt truly alive. They usually react to scripted events, or now they rely heavily on LLMs for dialogue, but the world itself rarely feels like it has genuine internal consistency. The conversations may sound human, yet the characters often don't behave like coherent individuals.

That left me with a question:

If I wanted to build virtual characters that felt genuinely human, where would I even begin?

My conclusion was that I first needed to understand what makes us human.

So instead of designing prompts, I began studying my own way of thinking and trying to decompose it into systems that a machine could execute. Aeris became an attempt to translate that into an architecture rather than into a single AI model.

The goal isn't to prove that an LLM can think.

The goal is to build a cognitive simulation whose assumptions can be inspected, questioned, replaced and improved over time.

One of the main architectural decisions comes from that philosophy.

The simulation itself is deterministic. Every change in the world comes from systems such as perception, memory, affect, goals and reasoning. The language model never changes reality—it only verbalizes an already computed internal state.

That decision came after looking at several AI projects and Skyrim AI mods. While I liked how natural the dialogue could become, I often felt something was missing: the language sounded human, but the behavior behind it wasn't always grounded in a consistent world model.

I wanted to solve that at the architectural level instead of trying to patch it with better prompts.

That's also why the project uses an ECS architecture. I originally came from object-oriented programming, but after researching large-scale simulations and data-oriented design, ECS seemed like the right foundation for the kind of complexity I wanted to achieve. It forced me to learn a completely different way of thinking, but it also made the architecture much more scalable.

Another design choice is the extensive use of contracts and architecture documents. They're not there just for documentation—they exist so that months later I can still understand why a design decision was made, question it if necessary, and evolve the project without losing its reasoning.

Ultimately, my philosophy for Aeris is simple:

I want virtual worlds to feel alive.

I want characters to behave according to coherent internal processes instead of only producing convincing dialogue.

And I want the cognitive model itself to be replaceable as research advances. If future work provides a better explanation of human cognition, the engine should be able to adopt it without redesigning everything else.

At this stage, I'm not looking for praise.

I'm looking for criticism.

If you think the architecture is flawed, I'd like to know why.

If you see conceptual mistakes, that's even more valuable.

If you disagree with the cognitive model, I'd like to discuss it.

If you think some algorithms should be redesigned, I'd appreciate your perspective.

And if the project interests you enough to contribute code, review documentation, or simply follow its progress, I'd be grateful. Right now the project is still in an early stage, and building a community around thoughtful technical discussion would be one of the best outcomes I could hope for.

Thanks for taking the time to read this.

u/zetario13 — 13 days ago
▲ 16 r/NixOS

I have 16, studying CCNA, started NixOS 2 months ago. Now I have a security.nix with 20 hardening sections. Roast my config.

Context: I'm 16, from Costa Rica, studying at a technical high school (COVAO), currently in my first period of CCNA. I've been using Linux for a while: Ubuntu → Arch → CachyOS → NixOS.

Why NixOS? I broke my system messing around and lost an important essay. That was the last straw. I needed something reproducible where "git checkout + nixos-rebuild switch" is my safety net.

Two weeks in, I had a working system. Two months later, this is what I have:

---

Repo: github.com/Cedrick-Coto/NixOs-Configuration

What's in it:

- Flakes + Home Manager + Hyprland (modular, 8 submodules)

- Noctalia Shell, Catppuccin theming, SDDM

- Gaming stack: Steam, Lutris, Bottles, Proton

- Dev tools: Python, Node.js, Neovim, Emacs, VSCodium

The new addition — security.nix with 20 sections:

  1. Firewall (nftables, rate limiting for SSH)

  2. SSH hardening (no root, no password, strong ciphers)

  3. Fail2ban (brute-force protection)

  4. Kernel hardening (ASLR, memory protection, network security params)

  5. auditd (file integrity monitoring for /etc/passwd, sshd_config, /boot...)

  6. AppArmor (MAC, currently in complain mode)

  7. Automatic security updates

  8. AIDE (file integrity)

  9. Restrictive umask

  10. Secure sudo (password required, logging)

  11. Disabled unnecessary services

  12. Logging (rsyslog + logrotate)

  13. User resource limits

  14. Blacklisted kernel modules (cramfs, dccp, sctp, usb-storage...)

  15. Security tools (lynis, nmap, wireshark, chkrootkit)

  16. NTP sync

  17. Core dumps disabled

  18. Secure Boot (placeholder)

  19. Monitoring (placeholder for Wazuh)

  20. TODO for next steps

Also documented:

- A 6-month cybersecurity roadmap (Fase 1: hardening & TryHackMe, Fase 2: offensive, Fase 3: defensive, Fase 4: specialization)

- GTD + Zettelkasten workflow (org-mode + Obsidian, 1000+ lines)

- Two philosophical essays I wrote along the way (yes, I know — unexpected)

---

What I'm looking for:

- What's missing in my security.nix? What did I get wrong?

- If you were 16 again and wanted to get into cybersecurity, what would you do differently?

- Any tips on balancing study (CCNA) + personal projects + gym?

Be honest. I can take it. That's the whole point of posting here.

reddit.com
u/zetario13 — 3 months ago