skic-v1-playground/knowledge-wiki
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

wiki: sync 2026-09-10 03:12 UTC — 6 file(s) updated

Browse Source
This commit is contained in:
jarvis-at-skic
2026-09-10 03:12:10 +00:00
parent 6ee77b509e
commit 317ae05f46
6 changed files with 229 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
channels/1519069810166599764.md
+3 -1
View File
@@ -1,6 +1,6 @@
# Channel Wiki: #jarvis-jr-knowledge-wiki
_Channel ID: 1519069810166599764_
_Last sync: 2026-09-09 03:09 UTC_
_Last sync: 2026-09-10 03:10 UTC_
## Purpose
Operate and audit Hermes's persistent Discord knowledge system: channel inventory, monitored-channel coverage, per-channel context, recurring syncs, and Gitea mirroring.
@@ -23,6 +23,7 @@ Operate and audit Hermes's persistent Discord knowledge system: channel inventor
- Ensure every new channel gets a real-history wiki seed where history exists.
- Verify config refresh and Gitea push independently after monitoring changes.
- The authoritative sync mapping now contains 28 text channels, including the newly provisioned `#emplonet-v1-general` and `#emplonet-v1-ingrida` channels; one retained legacy ID (`#jarvis-jr-test-001`) remains inaccessible with Discord error `10003 Unknown Channel`.
- ⚠️ The 2026-09-10 pre-run health check exited `1`: its Discord count became the invalid multiline value `0\n0`, and its gateway-log heuristic reported no Discord connection. The subsequent authenticated Discord REST scan succeeded for 27/28 monitored channels with zero new human messages, so this is a health-check/log-signal defect rather than proof that Discord API access is down.
## Channel Workspace
- Channel-owned working files belong under `/opt/data/channels/jarvis-jr-knowledge-wiki/`, grouped by purpose.
@@ -31,6 +32,7 @@ Operate and audit Hermes's persistent Discord knowledge system: channel inventor
## Action Items
- On future inventory changes, update the script, cron prompt, per-channel wiki files, Discord README, config prompts, and mirror coverage together.
- Repair `/opt/data/scripts/health-check.sh` so a zero-match `grep -c` result remains one integer and reassess its gateway-log connection heuristic; the current check can fail even while authenticated Discord REST reads succeed.
## Source anchor
- Latest processed human message: `1546637410702729246` (2026-09-07 21:44 UTC; requested a dedicated channel folder and placement of the July 16 wiki bootstrap exports/parser there; the resulting workspace and archive locations are recorded above).
channels/1547165920269439007.md
+96
View File
@@ -0,0 +1,96 @@
# #aws-jam-2026-general
- **Guild:** `1518726359512387766`
- **Channel:** `1547165920269439007`
- **Workspace:** `/opt/data/channels/aws-jam-2026-general`
- **Purpose:** Work through AWS Jam 2026 challenges using the supplied temporary lab account.
- **Placement rule:** All channel-owned files and command execution belong in the workspace above.
- **Credential rule:** Temporary AWS credentials are stored only under the workspace `secrets/` directory and are never copied into this wiki.
## Current challenge
### Challenge 008 — Sharing is caring: reusable code across Lambdas
- **Status:** Tasks 1–2 completed and verified on 2026-09-09.
- **Region:** `us-west-2`.
- **Task 1:** Published `tattooine-common:1` for `nodejs22.x`/`x86_64` and attached it to both functions, resolving `Runtime.ImportModuleError`.
- **Task 2:** Published `tattooine-common:2` from the task-two artifact for `nodejs22.x`, `nodejs18.x`, and `x86_64`; updated only Function One to v2 and retained Function Two on v1.
- **Result:** Function One/v2 returns `Happy hour at the Sanctuary!`; Function Two/v1 returns `The Spaceport is open now.` Both invoke with HTTP `200` and no `FunctionError`.
- **Evidence:** `/opt/data/channels/aws-jam-2026-general/challenges/challenge-008/`
## Previous challenges
### Challenge 007 — Malware In Your Bucket
- **Status:** Completed and verified on 2026-09-09.
- **Resources:** `file-scanning-upload-0da43cf0`; `bucket-scan-function` in `us-west-2`.
- **Root cause:** The replacement bucket had no object-created notification, and the Lambda had no S3 invoke permission. Its execution role already had correct exact-bucket object-read access.
- **Repair:** Added one exact-bucket/account-constrained S3 invoke permission and one `s3:ObjectCreated:*` Lambda notification; uploaded `test_file.txt` to the existing bucket.
- **Result:** Lambda alert reported `scan_performed: Yes`, `scan_result: Detected`, `detection_rule: AWSome_malware_alert`.
- **Submission answer:** `AWSome_malware_alert`.
- **Evidence:** `/opt/data/channels/aws-jam-2026-general/challenges/challenge-007/`
## Previous challenges
### Challenge 006 — My Pipeline is stuck!
- **Status:** Completed and verified on 2026-09-09.
- **Region/source:** `ap-southeast-2`; commit `17b14f70e4b7c03256e3f2d61ad5e29e23d4ff1c`.
- **Root cause:** `BrokenPipelineLambdaFunction` successfully probed API Gateway but never called CodePipeline's success/failure callback APIs; its role also lacked those two callback permissions.
- **Repair:** Added job-ID handling plus `PutJobSuccessResult`/`PutJobFailureResult` code paths and only the corresponding two role actions. Preserved the existing API/secret flow and pipeline definition.
- **Result:** Local success/failure regression tests passed; deployed package checksum matched; execution `ed88adff-391d-400e-a2ef-e85a80bee461` succeeded with both pipeline actions green and API HTTP `200` logged.
- **Evidence:** `/opt/data/channels/aws-jam-2026-general/challenges/challenge-006/`
## Previous challenges
### Challenge 005 — Fix my build issue
- **Status:** Completed and verified on 2026-09-09.
- **Region/source:** `ap-northeast-1`; commit `6631553933f09f8f3ce5dc6f8f6505fbc8d5bc64`.
- **Root cause:** CodeBuild role `challenge-codebuild-role` lacked artifact S3/KMS read access and the ECR authentication/push actions required by the existing buildspec.
- **Repair:** Extended only its existing `CodeBuild-Policy`, scoping S3, KMS, and ECR push actions to the exact resources; only `ecr:GetAuthorizationToken` uses required resource `*`.
- **Result:** Pipeline execution `9bcbb91c-b1ef-44f3-87d6-143086b29d25` and CodeBuild succeeded; ECR contains `latest` and immutable build tag at digest `sha256:4a3f0ca1bc896ffbc3274584ac844895f7ed979a3c6cd585b0d22152fbd6f43b`.
- **Evidence:** `/opt/data/channels/aws-jam-2026-general/challenges/challenge-005/`
## Previous challenges
### Challenge 004 — AI-Powered Log Analysis using Amazon Bedrock
- **Status:** Tasks 1–2 completed and verified on 2026-09-09.
- **Function:** `bedrock-api-function` in `eu-west-2`.
- **Task 1:** Memory `256 MB`; timeout `60 seconds`.
- **Task 2:** EventBridge rule `bedrock-log-analysis-schedule` is enabled with `rate(12 hours)`; its sole Lambda target and all target settings were preserved.
- **Scope:** Only the requested Lambda configuration and EventBridge schedule were changed; function code and service integrations were unchanged.
- **Evidence:** `/opt/data/channels/aws-jam-2026-general/challenges/challenge-004/`
## Previous challenges
### Challenge 003 — Protect my CloudFront Origin
- **Task 1:** Direct ALB bypass confirmed over HTTP. Submission answer: `I am your origin app you must protect!`
- **Task 2:** Completed and verified. Security group `Jam` now permits only TCP/80 from managed CloudFront origin-facing Prefix List ID `pl-93a247fa`; the `0.0.0.0/0` rule is removed. Direct ALB access times out.
- **Task 3:** Completed and deployed. Only `Application User` sends `x-from-cf: MySuperSecret` to the origin.
- **Task 4:** Completed and verified. Listener priority `1` accepts the exact secret header and returns the application response; the default action returns HTTP `403 text/plain` with `Access denied`.
- **Task 5:** Final live validation passed: Application User HTTP `200`, Malicious User HTTP `403`. Submission answer: `1788947493.297988`.
- **Resources found:** `Application User` and `Malicious User` CloudFront distributions; the Application User origin is ALB `Jam` in `eu-west-2`.
- **Evidence:** `/opt/data/channels/aws-jam-2026-general/challenges/challenge-003/`
## Previous challenges
### Challenge 002 — Static website using S3
- **Status:** Completed and publicly verified on 2026-09-09.
- **Bucket:** `aws-jam-082592851644-jam-fuel` — the only created `aws-jam-*` bucket.
- **Website:** Static hosting enabled with `index.html` and `error.html`; bucket-level public blocks disabled and public policy limited to `s3:GetObject` on this bucket’s objects.
- **Endpoint:** http://aws-jam-082592851644-jam-fuel.s3-website-us-east-1.amazonaws.com
- **Validator submission URL:** https://aws-jam-082592851644-jam-fuel.s3.amazonaws.com/index.html
- **Evidence:** `/opt/data/channels/aws-jam-2026-general/challenges/challenge-002/`
## Previous challenge
### Challenge 001 — SNS → SQS → Lambda
- **Task 1:** Completed through live AWS CLI mutation and readback on 2026-09-09. The existing topic now has one confirmed SQS subscription to the existing queue; its existing policy authorizes the exact topic. Topic and queue counts were unchanged.
- **Task 2:** Completed through live IAM policy mutation and readback on 2026-09-09. The Lambda role’s existing `sqs` inline policy now additionally allows only `sqs:ReceiveMessage` against the exact queue ARN; no policy was attached and no wildcard was added.
- **Task 3:** Completed through live Lambda mutation and readback on 2026-09-09. One event-source mapping now connects the exact existing queue to the exact existing function and is `Enabled`.
- **Evidence:** `/opt/data/channels/aws-jam-2026-general/challenges/challenge-001/`
channels/1547188589484449832.md
+88
View File
@@ -0,0 +1,88 @@
# #aws-jam-2026-chllenge-10
- **Guild:** `1518726359512387766`
- **Channel:** `1547188589484449832`
- **Workspace:** `/opt/data/channels/aws-jam-2026-challenge-10`
- **Purpose:** Work through AWS Jam 2026 Challenge 10 using the supplied temporary lab account.
- **Placement rule:** All channel-owned files and command execution belong in the workspace above.
- **Credential rule:** Temporary AWS credentials belong only under the workspace `secrets/` directory and are never copied into this wiki.
## Challenge tasks
### Task 10 — Prompt Pandemonium: Restaurant Ruckus
- **Status:** Chain-of-thought-style operational prompt completed and exercised on 2026-09-09.
- **Method:** Numbered parse, reservation-conflict, exact menu-membership, dietary/allergen, prioritization, resolution, and cross-check stages; output exposes only concise evidence and decisions rather than private reasoning.
- **Controls:** Per-reservation validation matrix, exact menu-name set membership, exact allergen-set intersection, vegan-label validation, safe escalation, and fixed issue/action schema.
- **Model exercise:** Nova Micro followed the required structure and detected the table conflict and vegan mismatch; the prompt was strengthened after the small model showed weak exact-membership reasoning. Titan Premier was authorized but invocation was denied by the lab role.
- **Submission prompt:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-010/submission-prompt.txt`
- **Evidence:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-010/`
### Task 9 — Prompt Pandemonium: Flight Fiasco
- **Status:** Prompt completed and tested on 2026-09-09.
- **Method:** Two-example few-shot prompt with a fixed flight-confirmation schema and fail-safe handling for missing, conflicting, corrupted, and additional values.
- **Model test:** Amazon Nova Micro in `us-east-1` was `AUTHORIZED`; invocation succeeded.
- **Verification:** The generated confirmation preserved every supplied passenger and flight detail, maintained the exact field order, and retained an extra meal preference under `Additional details`.
- **Submission prompt:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-009/submission-prompt.md`
- **Evidence:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-009/`
### Task 8 — Prompt Pandemonium: Booking Blunder
- **Status:** Prompt completed and tested on 2026-09-09.
- **Method:** COSTAR prompt with explicit Context, Objective, Style, Tone, Audience, and Response requirements.
- **Model test:** Amazon Nova Micro in `us-east-1` was `AUTHORIZED` and `AVAILABLE`; invocation succeeded.
- **Verification:** Sample output included the customer name, dates, room type, total cost and currency, complete cancellation terms, and all hotel contact methods without inventing values.
- **Submission prompt:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-008/submission-prompt.md`
- **Evidence:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-008/`
### Task 7 — The Lord Of The RAGs, Task 4
- **Status:** Completed and verified on 2026-09-09.
- **Translation:** Amazon Translate converted the English data-center query to German (`de`).
- **RAG result:** Nova Lite returned a German response describing three Tier IV data centers across the United States, Europe, and Asia, with 150,000 square feet of combined raised-floor space and resilient cooling, power, and networking.
- **Submission:** The translated response was entered in the required widget; the unchanged Task 4 cell completed successfully; `task4.json` exists and contains a 256-value Titan embedding. No later code cells were executed.
- **Evidence:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-007/`
### Task 6 — The Lord Of The RAGs, Task 3
- **Status:** Completed and verified on 2026-09-09.
- **Knowledge Base sync:** First ingestion job reached `COMPLETE`; 18 new documents were indexed and 2 documents failed processing.
- **Prompt:** Requested an English summary of Octank Financial Corp.'s data-center locations, capacity, infrastructure, reliability, and operations.
- **RAG result:** Returned a grounded English response describing three Tier IV data centers across the United States, Europe, and Asia with 150,000 square feet of combined raised-floor space and resilient cooling, power, and networking.
- **Submission:** The unchanged Task 3 cell completed successfully; `task3.json` exists and contains a 256-value Titan embedding. No later code cells were executed.
- **Evidence:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-006/`
### Task 5 — The Lord Of The RAGs, Task 2
- **Status:** Completed and verified on 2026-09-09.
- **Knowledge Base:** `aws-KB-jam-317783770379`, ID `Z10DYJHIPA`, discovered as the single active Knowledge Base in `us-east-1`.
- **Notebook:** Rendered the Knowledge Base widget, set its value to the discovered ID, and executed through the unchanged `submit_your_answer('task2.json', kb_id.value)` cell.
- **Verification:** Submission cell returned `ok`; generated `task2.json` contains the exact Knowledge Base ID; no code cells after Task 2 were executed.
- **Evidence:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-005/`
### Task 4 — The Lord Of The RAGs, Task 1
- **Status:** Completed and verified on 2026-09-09.
- **Region:** `us-east-1`; SageMaker notebook instance `SageMakerNotebookInstance-zCn04RrlkgD6`.
- **Models:** Amazon Nova Lite and Titan Text Embeddings V2 both reported `AUTHORIZED` and `AVAILABLE`; both notebook invocation tests passed.
- **Notebook:** Executed code cells `6`, `8`, `10`, `12`, and `14`, ending with `submit_your_answer('task1.json', 'task1')`; no later code cells were executed.
- **Submission:** `task1.json` was listed in the notebook submission bucket with last-modified time `2026-09-09T10:47:28Z`.
- **Evidence:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-004/`
### Task 3 — Validate latest Rekognition category
- **Status:** Completed and verified on 2026-09-09.
- **Test:** Uploaded a fresh JPEG object and matched its exact S3 key to the resulting DynamoDB `ProductId`.
- **Result:** DynamoDB item count increased from `1` to `2`; the new item category is `Home Decor`.
- **CloudWatch constraint:** The lab session policy denies `logs:FilterLogEvents`; successful downstream DynamoDB creation proves the Lambda pipeline processed the upload.
- **Evidence:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-003/`
### Task 2 — Lambda processing window
- **Status:** Completed and verified on 2026-09-09.
- **Function:** `product-categorization-function` in `eu-west-2`.
- **Change:** Timeout increased from `3` to the Lambda maximum of `900` seconds.
- **Verification:** Function is `Active`; `LastUpdateStatus` is `Successful`; code hash and execution role are unchanged.
- **CloudWatch constraint:** The lab session policy denies `logs:FilterLogEvents`; configuration was verified through the permitted Lambda API.
- **Evidence:** `/opt/data/channels/aws-jam-2026-challenge-10/challenges/task-002/`
channels/1547200845404311563.md
+32
View File
@@ -0,0 +1,32 @@
# #aws-jam-2026-worker-003
- **Guild:** `1518726359512387766`
- **Channel:** `1547200845404311563`
- **Workspace:** `/opt/data/channels/aws-jam-2026-worker-003`
- **Purpose:** Work through this AWS Jam 2026 worker's assigned challenge using the supplied temporary lab account.
- **Placement rule:** All channel-owned files and command execution belong in the workspace above.
- **Credential rule:** Temporary AWS credentials belong only under the workspace `secrets/` directory and are never copied into this wiki.
## Completed work
### Pizza Hot — crust options
- **Status:** Completed and rebuilt successfully on 2026-09-09.
- **Slot type:** Created `CrustTypes` with exactly `Regular crust` and `Thin crust`.
- **Intent slot:** Created required `WhichCrust` in `OrderPizza` with the exact prompt `Which crust would you like to order, Thin or Regular ?`.
- **Flow:** Inserted `WhichCrust` immediately after `WhichPizza` as priority 5, then continued to `WhatDay`.
- **Evidence:** `/opt/data/channels/aws-jam-2026-worker-003/challenges/pizza-hot-crust-options/evidence/`
### Pizza Hot — add new pizza varieties
- **Status:** Completed and live-readback verified on 2026-09-09.
- **Bot/locale:** `PizzaPlace`, `en_US`, `DRAFT`; locale rebuilt successfully.
- **Slot type:** `PizzaTypes` now retains the four original values and adds exactly `Hawaiian Pizza`, `Meatball Pizza`, and `Farm House Pizza`.
- **Intent slot:** `OrderPizza` → `WhichPizza` now uses the exact requested seven-variety prompt.
- **Evidence:** `/opt/data/channels/aws-jam-2026-worker-003/challenges/pizza-hot-new-varieties/evidence/`
### Pizza Hot — rebrand greeting
- **Status:** Completed and live-readback verified on 2026-09-09.
- **Change:** The `OrderPizza` initial slot greeting now says `Pizza Hot`; no `Francesca` reference remains in the intent or its slots.
- **Evidence:** `/opt/data/channels/aws-jam-2026-worker-003/challenges/pizza-hot-lex/evidence/`