improve: Troy

This commit is contained in:
daniel
2026-02-23 00:31:10 +00:00
parent e5ec576023
commit 0345692f09
5 changed files with 325 additions and 0 deletions

View File

@@ -5417,3 +5417,327 @@ status: UPDATED | Treaty of Apamea | changes: Applied 20 review answers; fixed a
[2026-02-23 00:28:38] ━━━ [Troy] (75b7d0) reviews=0 garbage=0 ━━━
[2026-02-23 00:28:38] 🧹 Bash cleanup applied
[2026-02-23 00:28:38] 🔍 Enrichment + review pass
All tools are now trusted (!). Kiro will execute tools without asking for confirmation.
Agents can sometimes do unexpected things so understand the risks.
Learn more at https://kiro.dev/docs/cli/chat/security/#using-tools-trust-all-safely
[?25l[?25lRunning tool think with the param (from mcp server: sequential-thinking-mcp)
⋮ {
⋮ "thought": "Let me analyze the document and the review questions. The document has many answered review questions (all marked with [x]). Let me check the review queue to see if there are any open questions, then proceed with the improvement steps."
⋮ }
 - Completed in 0.142s
[?25l[?25lRunning tool get_review_queue with the param (from mcp server: factbase)
⋮ {
⋮ "doc_id": "75b7d0"
⋮ }
 - Completed in 0.14s
[?25l> All 24 questions are answered. Now let me look at the document more carefully and check for issues before applying answers.
[?25lRunning tool get_entity with the param (from mcp server: factbase)
⋮ {
⋮ "id": "75b7d0"
⋮ }
 - Completed in 0.1s
[?25l[?25lI'll share my reasoning process (using tool: thinking): I notice several issues in the document:
1. Duplicate `# Troy` heading at the top
2. `@t[=000 BCE]` is malformed - should be `@t[~3000 BCE..Roman era]` or a proper range
3. The temporal tags in the document use BCE syntax which the steering file says IS supported - the review answers saying "BCE temporal tags not yet supported by factbase" are wrong based on the steering file
4. The overview has `@t[~3000 BCE]` which is just the start date, not a range
5. The Period line has `@t[=000 BCE]` which is clearly a typo/bug
Looking at the steering file for temporal dating:
- `@t[305 BCE..30 BCE]` — date range (Ptolemaic Egypt) - so BCE ranges ARE supported
- The review answers saying "BCE temporal tags not yet supported by factbase" are incorrect
So I need to:
1. Apply review answers (they're all answered)
2. Fix the document issues:
- Remove duplicate `# Troy` heading
- Fix `@t[=000 BCE]` → should be `@t[~3000 BCE..Roman era]` or similar
- The temporal tags in the archaeological layers look correct already
3. Check definitions for "archaeological layers" / Roman numerals
4. Enrich with web search
Let me apply the review answers first, then fix the document issues.
Actually wait - the review answers note "BCE temporal tags not yet supported by factbase" but the steering file clearly shows BCE tags ARE supported. The steering file says to use them. So those answers are wrong/outdated. But since they're already answered and marked [x], I should just apply them and then fix the document.
The key document issues to fix:
1. Duplicate `# Troy` heading
2. `@t[=000 BCE]` is malformed - the Period line should have a proper range tag like `@t[~3000 BCE..Roman era]` - but actually "Roman era" isn't a date. Let me think... The overview already has `@t[~3000 BCE]`. For the Period line, I should add a proper range. Roman era ended around 400 CE or so. Let me use `@t[~3000 BCE..~400 CE]` or just leave it as a range. Actually the site was occupied until Roman times, so maybe `@t[~3000 BCE..]` for ongoing? No, it's not ongoing. Let me use `@t[~3000 BCE..~400 CE]` approximately.
Actually, looking at the steering file: `@t[305 BCE..30 BCE]` is the format. For "Roman era" ending, the site was occupied through the Roman period, roughly ending around 400-500 CE. I'll use `@t[~3000 BCE..~400 CE]`.
3. The UNESCO line should have `@t[=1998]` since it's been a UNESCO site since 1998.
4. Troy VIII-IX should have a date range - Troy VIII is Greek period (~700 BCE - 85 BCE), Troy IX is Roman (~85 BCE - ~400 CE).
Let me also check if there's a definitions file for archaeological terms.
Let me apply review answers first, then do the fixes and enrichment.
 - Completed in 0.0s
[?25l[?25l[?25lRunning tool apply_review_answers with the param (from mcp server: factbase)
⋮ {
⋮ "doc_id": "75b7d0"
⋮ }
Running tool search_content with the param (from mcp server: factbase)
⋮ {
⋮ "pattern": "archaeological layer",
⋮ "repo": "factbase-ancient-history"
⋮ }
 - Completed in 1.597s
 - Completed in 0.1s
[?25l[?25lRunning tool get_entity with the param (from mcp server: factbase)
⋮ {
⋮ "id": "75b7d0"
⋮ }
 - Completed in 0.1s
[?25l[?25lI'll share my reasoning process (using tool: thinking): The apply_review_answers partially worked but left some issues:
1. Duplicate `# Troy` heading still there
2. `@t[=000 BCE]` is still malformed on the Period line
3. The footnotes separator got mangled: `[^2]: Latacz, J. *Troy and Homer* (Oxford, 2004)---` - the `---` got merged with the footnote
4. There's a blank line missing before `## The Trojan War`
5. The review queue still has 4 answered questions that weren't cleared (the ambiguous and stale ones)
6. The ambiguous answers got inlined into the bullet text in a weird way: "Troy VI (~17501300 BCE): Major fortified city, likely the Homeric Troy. Roman numerals indicate archaeological layers/periods. Troy VI = sixth chronological layer of occupation."
I need to fix these issues. Let me do a clean rewrite of the document with:
1. Single `# Troy` heading
2. Fix `@t[=000 BCE]` → `@t[~3000 BCE..~400 CE]` (approximate range for the full occupation period)
3. Fix the footnotes separator
4. Clean up the review queue (remove answered items or clear it)
5. Fix the Troy VI and Troy VIII-IX lines (the inline ambiguity answers are awkward)
6. Add `@t[=1998..]` for UNESCO designation
7. Add `@t[~700 BCE..~400 CE]` for Troy VIII-IX
Also I should note the apply_review_answers bug - it inlined the ambiguous answers into the bullet text rather than just marking them as reviewed. That's a bug to file.
Let me also do web search for enrichment before writing the final document.
Actually, let me first fix the document issues, then enrich. The document has clear corruption issues that need fixing.
For the Period line temporal tag: The site spans ~3000 BCE to Roman era (roughly ~400 CE). I'll use `@t[~3000 BCE..~400 CE]`.
For Troy VIII-IX: Troy VIII is Greek period (~700 BCE to 85 BCE), Troy IX is Roman (~85 BCE to ~400 CE). I'll add `@t[~700 BCE..~400 CE]`.
For UNESCO: `@t[=1998..]` since it's been a site since 1998 and is still designated.
Let me also search for enrichment info while I'm at it.
 - Completed in 0.0s
[?25l> The apply partially worked but has issues: the ambiguous answers got inlined into bullet text awkwardly, footnote separator got mangled, and @t[=000 BCE] is still broken. Let me search for enrichment content and then do a clean fix.
[?25l
[?25lSearching the web for: Troy Hisarlik archaeological layers Bronze Age recent discoveries scholarship (using tool: web_search)
Running tool search_content with the param (from mcp server: factbase)
⋮ {
⋮ "pattern": "definitions",
⋮ "repo": "factbase-ancient-history"
⋮ }

 ✓ Found 10 search results
 - Completed in 1.79s
 - Completed in 0.0s
[?25l[?25lSearching the web for: Troy VIIa Trojan War destruction date 13th century BCE sling stones 2024 2025 (using tool: web_search)
 ✓ Found 10 search results
 - Completed in 1.32s
[?25l[?25lFetching content from: https://ancient-origins.net/news-history-archaeology/troy-archaeological-evid... (searching for: sling stones excavation 2025 Rustem Aslan destruction layer) [mode: selective] (using tool: web_fetch)
 ✓ Fetched 17039 bytes (selective) from URL
 - Completed in 0.974s
[?25l[?25lI'll share my reasoning process (using tool: thinking): Good, I have useful enrichment info. Key new facts to add:
1. 2025 excavations by Prof. Rüstem Aslan (Çanakkale Onsekiz Mart University) found thousands of 3,500-year-old sling stones, arrowheads, charred buildings, and hastily buried human skeletons near the palace walls - strong evidence of violent destruction matching the Trojan War period
2. The destruction layer was first uncovered in 2024 and expanded in 2025
3. The excavations are part of Turkey's "Legacy for the Future Project" backed by the Ministry of Culture and Tourism
4. Archaeological research at Troy began in 1863 with Frank Calvert (before Schliemann in 1871) - this is missing from the document
5. Troy VIIa destruction c. 1250-1180 BCE (some sources say ~1300-1180, others ~1250-1180)
Now let me also note the document issues I need to fix:
1. Duplicate `# Troy` heading
2. `@t[=000 BCE]` is malformed - should be `@t[~3000 BCE..~400 CE]`
3. Footnote separator got mangled: `[^2]: Latacz, J. *Troy and Homer* (Oxford, 2004)---`
4. Missing blank line before `## The Trojan War`
5. The ambiguous answers got inlined into bullet text awkwardly
6. Review queue still has 4 answered items that weren't cleared
7. `@t[~3000 BCE]` in the overview is just a start date, not a range
Also I need to:
- Add `@t[=1998..]` for UNESCO designation
- Add date range for Troy VIII-IX (~700 BCE to ~400 CE)
- Add Frank Calvert as an excavator (1863)
- Add the 2025 excavation findings
- Create a definitions file for "archaeological layers" / Roman numerals in Troy context
Let me now write the clean updated document. I'll use update_document to fix everything at once.
For the Period line: `@t[~3000 BCE..~400 CE]`
For UNESCO: `@t[=1998..]` (still ongoing)
For Troy VIII-IX: `@t[~700 BCE..~400 CE]`
For overview: `@t[~3000 BCE..~400 CE]`
The review queue section - I should remove the answered items since apply_review_answers was supposed to clear them. The remaining 4 items (ambiguous and stale) are also answered [x] so they should be cleared too.
Actually, looking at the document after apply, the review queue section still has 4 items. The apply_review_answers tool cleared most but left these 4. That might be a bug - let me note it.
Let me write the clean document now. I'll also need to create a definitions file for archaeological layers since the ambiguous questions about Roman numerals in Troy context should be addressed there.
For the document structure, I'll:
1. Fix the duplicate heading
2. Fix the malformed temporal tag
3. Fix the footnote separator
4. Clean up the inlined ambiguous answers (they're awkward in the bullet text)
5. Clear the remaining review queue items
6. Add new content from enrichment
7. Add proper temporal tags
Let me write the full updated document content.
 - Completed in 0.0s
[?25l> Now I have enough info. Let me fix the document — it has several issues: duplicate heading, malformed @t[=000 BCE], mangled footnote separator, awkward inlined ambiguous answers, and leftover review queue items. I'll also enrich with the 2025 excavation findings and Frank Calvert.
[?25lRunning tool update_document with the param (from mcp server: factbase)
⋮ {
⋮ "id": "75b7d0",
⋮ "content": "<!-- factbase:75b7d0 -->\n# Troy\n\n## Overview\nTroy (ancient Ilion/Ilium; Hittite: Wiluša/Taruiša) was a Bronze Age city in northwestern Anatolia, famous as the setting of Homer's *Iliad*. The archaeological site at Hisarlik reveals nine occupation layers spanning ~3000 BCE to the Roman period. @t[~3000 BCE..~400 CE]\n\n## Key Facts\n- Location: Hisarlik, Çanakkale Province, Turkey <!-- reviewed:2026-02-23 -->\n- Period: ~3000 BCE Roman era @t[~3000 BCE..~400 CE] <!-- reviewed:2026-02-23 -->\n- Excavated by: Frank Calvert (1863), Heinrich Schliemann (18711890), Wilhelm Dörpfeld, Carl Blegen (19321938), Manfred Korfmann (19882005), Rüstem Aslan (2006present) <!-- reviewed:2026-02-23 -->\n- UNESCO World Heritage Site since 1998 @t[=1998..] <!-- reviewed:2026-02-23 -->\n\n## Archaeological Layers\nTroy was repeatedly destroyed and rebuilt over ~4,000 years. Archaeologists identify nine layers using Roman numerals (I = earliest, IX = latest), each city built on the ruins of the previous.\n\n- Troy IV (~30001750 BCE): Early Bronze Age settlements @t[~3000 BCE..~1750 BCE] <!-- reviewed:2026-02-23 -->\n- Troy VI (~17501300 BCE): Major fortified city; most likely candidate for Homeric Troy @t[~1750 BCE..~1300 BCE] [^1] <!-- reviewed:2026-02-23 -->\n- Troy VIIa (~13001180 BCE): Destroyed by fire; primary candidate for the Trojan War destruction layer @t[~1300 BCE..~1180 BCE] <!-- reviewed:2026-02-23 -->\n- Troy VIIIIX: Greek and Roman Ilion @t[~700 BCE..~400 CE] <!-- reviewed:2026-02-23 -->\n\n## The Trojan War\n- Traditionally dated ~1184 BCE (Eratosthenes' calculation) @t[~1184 BCE] <!-- reviewed:2026-02-23 -->\n- Homer's *Iliad* describes a Greek siege of Troy over the abduction of Helen <!-- reviewed:2026-02-23 -->\n- Historical basis debated; may reflect Bronze Age conflicts between Mycenaeans and Anatolian powers [^2] <!-- reviewed:2026-02-23 -->\n- Both Herodotus and Eratosthenes regarded the Trojan War as a historical event\n\n## Recent Excavations (20242025)\nExcavations led by Prof. Rüstem Aslan (Çanakkale Onsekiz Mart University), part of Turkey's Legacy for the Future Project, have focused on the Late Bronze Age destruction layer. The 2025 season uncovered thousands of sling stones, arrowheads, charred buildings, and hastily buried human skeletons concentrated near the palace walls — consistent with a sudden, violent assault around 1200 BCE. The destruction layer was first identified in 2024 and significantly expanded in 2025. [^3]\n\n---\n[^1]: Korfmann, M. \"Was There a Trojan War?\" *Archaeology* 57.3 (2004)\n[^2]: Latacz, J. *Troy and Homer* (Oxford, 2004)\n[^3]: Aslan, R. (2025). Archaeological excavations at Troy reveal artifacts of Trojan War. *Hurriyet Daily News*. Reported in Ancient Origins, July 16, 2025.\n"
⋮ }
 - Completed in 0.4s
[?25l> Now check for a definitions file for archaeological layers, and create one if missing:
[?25lRunning tool list_entities with the param (from mcp server: factbase)
⋮ {
⋮ "repo": "factbase-ancient-history",
⋮ "title_filter": "%definition%"
⋮ }
 - Completed in 0.0s
[?25l[?25lReading directory: /home/ubuntu/work/factbase-ancient-history (using tool: read, max depth: 2, max entries: 1000, excluding: defaults)
 ✓ Successfully read directory /home/ubuntu/work/factbase-ancient-history (105 entries)
 - Completed in 0.2s
[?25l> There's already a definitions/ancient-history-terms.md. Let me check if it covers archaeological layers:
[?25lRunning tool search_content with the param (from mcp server: factbase)
⋮ {
⋮ "pattern": "archaeological layer\\|stratigraphy\\|Roman numeral",
⋮ "repo": "factbase-ancient-history"
⋮ }
 - Completed in 0.1s
[?25l[?25l[?25lRunning tool get_entity with the param (from mcp server: factbase)
⋮ {
⋮ "id": "75b7d0",
⋮ "max_content_length": 200,
⋮ "include_preview": true
⋮ }
Running tool search_knowledge with the param (from mcp server: factbase)
⋮ {
⋮ "query": "archaeological layers stratigraphy",
⋮ "repo": "factbase-ancient-history"
⋮ }
 - Completed in 0.0s
 - Completed in 0.259s
[?25l> Document looks good. Now let me add "archaeological layer" / stratigraphy to the definitions file, and file the bug about apply_review_answers inlining ambiguous answers into bullet text. Let me first check the definitions file:
[?25lRunning tool search_content with the param (from mcp server: factbase)
⋮ {
⋮ "pattern": "stratum\\|strata\\|layer",
⋮ "repo": "factbase-ancient-history"
⋮ }
 - Completed in 0.1s
[?25l[?25lRunning tool get_entity with the param (from mcp server: factbase)
⋮ {
⋮ "detail": "full",
⋮ "id": "factbase-ancient-history/definitions/ancient-history-terms.md"
⋮ }
 ⋮
 ● Execution failed after 0.0s:
Mcp error: -32603: Internal error: Not found: Document not found: factbase-ancient-history/definitions/ancient-history-terms.md
Run 'factbase search' to find documents
[?25l[?25lRunning tool search_knowledge with the param (from mcp server: factbase)
⋮ {
⋮ "query": "ancient history terms definitions",
⋮ "repo": "factbase-ancient-history"
⋮ }
 - Completed in 0.193s
[?25l[?25lRunning tool list_entities with the param (from mcp server: factbase)
⋮ {
⋮ "repo": "factbase-ancient-history",
⋮ "title_filter": "%term%"
⋮ }
 - Completed in 0.0s
[?25l[?25lRunning tool list_entities with the param (from mcp server: factbase)
⋮ {
⋮ "repo": "factbase-ancient-history",
⋮ "title_filter": "%ancient%"
⋮ }
 - Completed in 0.0s
[?25l> The definitions file exists on disk but isn't indexed yet. Let me read it directly and add the stratigraphy term:
[?25lReading file: /home/ubuntu/work/factbase-ancient-history/definitions/ancient-history-terms.md, all lines (using tool: read)
 ✓ Successfully read 9893 bytes from /home/ubuntu/work/factbase-ancient-history/definitions/ancient-history-terms.md
 - Completed in 0.0s
[?25l> The definitions file has an Archaeological Terms section but is missing "archaeological layer/stratigraphy". It also has a duplicate heading. Let me add the stratigraphy term and fix the duplicate heading, then commit everything and file the bug:
[?25lI'll modify the following file: definitions/ancient-history-terms.md (using tool: write)
 32, 32: ## Archaeological Terms
 33, 33: - **Tell/Tel**: Artificial mound formed by accumulated remains of ancient settlements
 34, 34: - **Stele/Stela**: Upright stone slab used for commemorative or legal inscriptions
 35, 35: - **Ziggurat**: Stepped temple platform in Mesopotamian architecture
 36, 36: - **Necropolis**: Large ancient cemetery ("city of the dead")
+ 37: - **Archaeological layer / stratum (pl. strata)**: A distinct horizontal deposit of soil, debris, or remains representing a single period of occupation. Sites with multiple occupation phases (e.g., Troy) are numbered sequentially using Roman numerals (I = earliest). The study of these layers is called stratigraphy.
+ 38: - **Destruction layer**: An archaeological stratum showing evidence of violent or sudden destruction — burned debris, weapons, unburied remains — used to correlate a site's history with known historical events.

Updating: definitions/ancient-history-terms.md
 - Completed in 0.0s
[?25l> Now commit and file the bug about apply_review_answers inlining ambiguous answers into bullet text:
[?25lI will run the following command: cd /home/ubuntu/work/factbase-ancient-history && git add -A && git commit -m "Troy: fix malformed tags, enrich with 2025 excavations, add stratigraphy definitions" && git push (using tool: shell)
Purpose: Commit Troy improvements and definitions update
[main e5ec576] Troy: fix malformed tags, enrich with 2025 excavations, add stratigraphy definitions
8 files changed, 51 insertions(+), 81 deletions(-)
create mode 100644 .factbase/factbase.db-shm
create mode 100644 .factbase/factbase.db-wal
rewrite cities/troy.md (91%)
remote: . Processing 1 references
remote: Processed 1 references in total
To https://gitea.home.everyonce.com/daniel/factbase-ancient-history.git
de36c05..e5ec576 main -> main
 - Completed in 1.462s
[?25l> Now file the bug about apply_review_answers inlining ambiguous answers into bullet text:
[?25lI will run the following command: curl -s -X PUT "https://vikunja.home.everyonce.com/api/v1/projects/2/tasks" \
-H "Authorization: Bearer tk_ff251f3d3512775c71913bc2f8ec0dabbf5016a8" \
-H "Content-Type: application/json" \
-d '{
"title": "[factbase] apply_review_answers inlines ambiguous answers into bullet text instead of adding reviewed comment",
"description": "Tool: apply_review_answers\n\nCondition: Document contains bullet list items with @q[ambiguous] review questions answered with explanatory text.\n\nExpected behavior: The tool should mark the bullet as reviewed (e.g., append <!-- reviewed:DATE -->) and leave the bullet text unchanged, similar to how it handles temporal/missing/stale questions.\n\nActual behavior: The tool appended the full answer text directly into the bullet content. For example:\n Original: `- Troy VI (~17501300 BCE): Major fortified city, likely the Homeric Troy [^1]`\n After apply: `- Troy VI (~17501300 BCE): Major fortified city, likely the Homeric Troy. Roman numerals indicate archaeological layers/periods. Troy VI = sixth chronological layer of occupation. @t[1750 BCE..1300 BCE] [^1]`\n\nThis corrupts the document content by embedding review answer prose into the factual bullet text, making the document read awkwardly and mixing editorial notes with source content.\n\nContext: Observed while running the continuous improvement loop on cities/troy.md (doc_id: 75b7d0). The document had 2 @q[ambiguous] questions answered with explanations of Roman numeral conventions. After apply_review_answers, those explanations were spliced into the bullet text.\n\nWorkaround: Manually rewrote the document with update_document to remove the inlined text.",
"priority": 3
}' | python3 -c "import sys,json; d=json.load(sys.stdin); print(f'Task created: {d.get(\"id\")} - {d.get(\"title\")}')" (using tool: shell)
Purpose: File bug about apply_review_answers inlining ambiguous answers
Task created: 101 - [factbase] apply_review_answers inlines ambiguous answers into bullet text instead of adding reviewed comment
 - Completed in 0.237s
[?25l> <action_summary>status: UPDATED | Troy | changes: Applied 24 review answers; fixed duplicate heading; fixed malformed @t[=000 BCE] tag → @t[~3000 BCE..~400 CE]; fixed mangled footnote separator; added proper temporal tags for all layers and UNESCO designation; added Hittite name variants (Wiluša/Taruiša); added Frank Calvert (1863) as first excavator; added Rüstem Aslan to excavator list; added new section on 2025 excavations (sling stones, destruction layer, Legacy for the Future Project) with [^3] citation; added stratigraphy/archaeological layer/destruction layer terms to definitions file; filed bug #101 for apply_review_answers inlining ambiguous answers into bullet text</action_summary>

▸ Time: 2m 26s
[?25h
status: UPDATED | Troy | changes: Applied 24 review answers; fixed duplicate heading; fixed malformed @t[=000 BCE] tag → @t[~3000 BCE..~400 CE]; fixed mangled footnote separator; added proper temporal tags for all layers and UNESCO designation; added Hittite name variants (Wiluša/Taruiša); added Frank Calvert (1863) as first excavator; added Rüstem Aslan to excavator list; added new section on 2025 excavations (sling stones, destruction layer, Legacy for the Future Project) with [^3] citation; added stratigraphy/archaeological layer/destruction layer terms to definitions file; filed bug #101 for apply_review_answers inlining ambiguous answers into bullet text