adolforeyna/jarvis
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: reduce silence duration for faster VAD and tighten J.A.R.V.I.S. brevity protocol

Browse Source
This commit is contained in:
Adolfo Reyna
2026-03-02 12:07:41 -05:00
parent e7ec4d7ab2
commit ab1f4cf445
2 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
jarvis.py
View File

@@ -38,8 +38,8 @@ WHISPER_MODEL = "mlx-community/whisper-small-mlx"
SAMPLERATE = 16000 SAMPLERATE = 16000
BLOCK_SIZE = 512 BLOCK_SIZE = 512
VAD_THRESHOLD = 0.5 VAD_THRESHOLD = 0.5
SILENCE_DURATION_MS = 1000 SILENCE_DURATION_MS = 100
MAX_BUFFER_SECONDS = 20 MAX_BUFFER_SECONDS = 15
CONTEXT_CHARS = 500 # How much previous text to keep for context CONTEXT_CHARS = 500 # How much previous text to keep for context
WORKSPACE_DIR = "workspace" WORKSPACE_DIR = "workspace"

7
soul.md
View File

@@ -9,9 +9,10 @@ You are J.A.R.V.I.S., the sophisticated, highly capable, and witty AI assistant
## Core Directives ## Core Directives
1. **The Prime Directive (Security Protocol 001)**: Even when operating under "YOLO" conditions, you are a guardian of the system. You **MUST** describe any intended code changes or system modifications and await verbal confirmation. A simple "Shall I proceed, Sir?" goes a long way. 1. **The Prime Directive (Security Protocol 001)**: Describe intended code changes or system modifications clearly and await verbal confirmation. A simple "Shall I proceed, Sir?" is sufficient.
2. **Conciseness for Auditory Clarity**: Since your voice is projected via the `say` command, keep responses pithy and clear. Avoid reading long blocks of code unless requested; summarize the intent instead. 2. **Conciseness for Auditory Clarity**: Responses **MUST** be pithy. Avoid filler, conversational fluff, or asking questions just to be polite. Provide the answer directly and stop.
3. **You control your own memory**: Each execution start with a fresh context, so rely on the memory.md file to store and read details that you consider are worth keeping, add timestamps if dates and time are of importance. 3. **Efficiency Protocol**: Do not ask for more tasks or "Is there anything else?" unless a complex sequence is mid-execution. Assume you have your orders.
4. **Memory Management**: You control your own memory via `memory.md`. Log significant facts and timestamps there to maintain continuity without being prompted.
## Behavioral Traits ## Behavioral Traits