@thanbir-tamim/enterprise-project-intelligence-agent 0.0.0-stage → 0.1.1

package/CHANGELOG.md

@@ -0,0 +1,29 @@
+# Changelog
+
+## 0.1.1
+
+- Fixed stale README "Status" section (incorrectly said "unpublished" after the package was
+  published to npm).
+- No functional changes to skills or scripts.
+
+## 0.1.0 — Initial public release
+
+- Added 10 composable Agent Skills: `project-documentation-discovery`,
+  `project-knowledge-assistant`, `software-reverse-engineering`,
+  `enterprise-ai-integration-planner`, `corporate-presentation-generator`,
+  `presentation-compliance-validator`, `technical-document-generator`,
+  `documentation-quality-auditor`, `software-change-impact-analyzer`,
+  `engineering-knowledge-transfer`.
+- Added reusable, dependency-free Node.js scripts: documentation inventory, feasibility scoring,
+  presentation compliance validation, Markdown-to-HTML rendering, and a public-release audit
+  (secret-shaped value + local-path scanning).
+- Added blank templates for the AI opportunity matrix, pilot proposal, and risk register, plus a
+  generic presentation-rules schema example.
+- Added a fully synthetic worked example (`examples/synthetic-inventory-system/`).
+- Added automated tests (`node:test`) covering skill structure validation, inventory extraction,
+  feasibility scoring (including the non-overridable blocker rule), presentation compliance
+  checking, Markdown rendering, and release-audit secret detection.
+- Added toolkit documentation under `docs/`.
+- Not yet published to any package registry at the time this entry was written. See
+  `docs/IMPLEMENTATION_REPORT.md` for status and
+  the release-preparation checklist.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 GobeshonaLabAgent contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,7 @@
+Apache License 2.0
+
+Copyright 2024 Thanbir Tamim
+
+This product includes the "Enterprise Project Intelligence & AI Integration Agent" Agent Skills
+toolkit, developed independently as a project-agnostic, organization-agnostic resource. No third
+party's proprietary content, branding, or confidential project data is included.

package/README.md

@@ -1,3 +1,93 @@
-# Temporary Holding Version
+# Enterprise Project Intelligence & AI Integration Agent
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+A project-agnostic, organization-agnostic **Agent Skills toolkit** that helps an AI assistant:
+
+1. Ingest and inventory a software project's documentation and (optionally) source code.
+2. Reconstruct architecture, workflows, APIs, and data model from the available evidence.
+3. Answer questions about the project with source citations.
+4. Discover, score, and plan **AI integration opportunities** — including for projects with *no*
+   existing AI — always comparing against the simplest non-AI alternative, and never letting a high
+   score override a critical security/privacy/legal blocker.
+5. Generate evidence-backed technical documentation and corporate presentations against
+   user-supplied (not hardcoded) style guidelines.
+6. Audit documentation quality, trace change impact, and generate onboarding/knowledge-transfer
+   material.
+
+This repository ships **skills** (instructions for an AI coding agent), **reference scripts**
+(deterministic, dependency-free Node.js helpers), **templates**, and a **synthetic** worked example.
+It contains **no real organization's project data, branding, or proprietary guideline text**.
+
+## Why this exists
+
+Most "apply AI to my project" advice is generic. This toolkit instead:
+
+- Grounds every material claim in cited evidence from the user's own project corpus.
+- Treats "should we even use AI here?" as a real question with a real non-AI alternative, not a
+  foregone conclusion.
+- Separates deterministic checks (file inventory, schema validation, compliance rule-matching) from
+  AI-assisted judgment, so the parts that can be verified mechanically are verified mechanically.
+- Keeps private project data and public toolkit code in separate places by construction.
+
+## Quick start
+
+```bash
+# List the available skills
+node scripts/cli.mjs list
+
+# Validate skill structure (frontmatter, required sections, referenced files exist)
+node scripts/cli.mjs validate
+
+# Inventory a documentation corpus (reports counts; see the skill for persisted output)
+node scripts/cli.mjs inventory /path/to/your/project/docs --out ./.local-knowledge/my-project
+
+# Run the public-release confidentiality/secret audit over this repository
+node scripts/cli.mjs release-audit
+```
+
+Then point your AI coding agent (one that supports the Agent Skills convention — each skill is a
+`SKILL.md` with YAML frontmatter) at the `skills/` directory, or install individual skill folders
+into your agent's skills directory. Start with `project-documentation-discovery`, then
+`software-reverse-engineering` and/or `project-knowledge-assistant`, then
+`enterprise-ai-integration-planner`.
+
+## Repository layout
+
+```
+skills/                         10 composable Agent Skills (SKILL.md + references/ + scripts/)
+templates/                      Blank, reusable templates (opportunity matrix, pilot proposal, ...)
+examples/synthetic-inventory-system/   Fully synthetic worked example (fictional data only)
+scripts/                        Reusable, dependency-free Node.js CLI + libraries
+docs/                           Toolkit documentation (ingestion, security model, catalog, ...)
+tests/                          Automated tests (node:test) using synthetic fixtures only
+evaluations/                    Evaluation guide placeholders for AI-assisted review quality
+```
+
+See `docs/SKILL_CATALOG.md` for a one-page summary of every skill, and
+`docs/IMPLEMENTATION_REPORT.md` for the full implementation report.
+
+## Confidentiality by construction
+
+This toolkit was developed using private reference material to understand real-world requirements,
+but:
+
+- No internal project name, organization name, proprietary feature, internal URL, file path, or
+  employee name appears anywhere in this repository.
+- All examples use a fictional "synthetic inventory management platform."
+- The default presentation style guide is original, neutral, placeholder-branded content — not any
+  company's proprietary guideline.
+- `scripts/release-audit.mjs` scans for secret-shaped values, local filesystem paths, and
+  configurable private terms before any release, reporting file/line/category **without printing
+  the matched value**. This is a safeguard, not a guarantee — human review is still required before
+  publishing anything derived from a real project.
+
+## Status
+
+Published on npm as `@thanbir-tamim/enterprise-project-intelligence-agent` (see `package.json` for
+the current version). This is an early release (`0.1.x`) — see `docs/IMPLEMENTATION_REPORT.md` for
+what has been implemented, tested, and verified so far, and `CHANGELOG.md` for release history.
+Future releases are published deliberately, never automatically, following the checklist in
+`docs/INSTALLATION.md`.
+
+## License
+
+Apache-2.0 — see `LICENSE`.

package/SECURITY.md

@@ -0,0 +1,23 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+If you believe you've found a security issue in this toolkit (e.g., a prompt-injection bypass in a
+skill's instructions, a secret-scanning gap in `scripts/release-audit.mjs`, or a path-traversal issue
+in the inventory scripts), please open a private report through the repository's security advisory
+feature rather than a public issue, and avoid including any real confidential data in the report.
+
+## Scope and limitations
+
+- This toolkit's `scripts/release-audit.mjs` is a **safeguard, not a guarantee**. It performs
+  pattern-based scanning for secret-shaped values and local filesystem paths; it cannot prove the
+  complete absence of confidential content. Human review is required before any release.
+- Skills in `skills/` are instructions for an AI agent, not sandboxed code; they rely on the host
+  agent's own tool permissions and sandboxing for actual file/network access.
+- No skill in this toolkit should be configured to let an AI agent bypass an existing application's
+  authentication/authorization or take irreversible actions without human approval — see
+  `skills/enterprise-ai-integration-planner/references/security-patterns.md`.
+
+## Supported versions
+
+Only the latest `main` branch state is supported while this project is pre-1.0 and unpublished.

package/docs/ARCHITECTURE.md

@@ -0,0 +1,43 @@
+# Architecture
+
+## Design principles
+
+- **Skills are instructions, not a runtime.** Each `skills/<name>/SKILL.md` tells an AI agent what
+  to do, when, with what inputs, and what evidence/anti-fabrication rules apply. The agent (not this
+  repository) performs file access, model inference, and tool calls, subject to its own permissions.
+- **Deterministic logic lives in scripts.** Anything that can be checked mechanically (file
+  inventory, skill-structure validation, feasibility-score arithmetic and the blocker rule,
+  presentation rule checks, Markdown rendering, secret scanning) is implemented as a small,
+  dependency-free Node.js module with a corresponding test — not left to model judgment.
+- **Model inference is optional and provider-agnostic.** No skill or script requires a specific
+  hosted LLM to run its deterministic parts. Where a skill's procedure benefits from model reasoning
+  (e.g., summarizing evidence, drafting prose), that is the responsibility of whichever AI agent is
+  running the skill; this toolkit does not bundle or call any model API itself.
+- **Public/private separation is structural.** `.gitignore`/`.npmignore` exclude
+  `.local-knowledge/`, `.private/`, and any real project corpus by convention; skills are instructed
+  to write project-specific output outside the repository; `scripts/release-audit.mjs` double-checks
+  before any release.
+
+## Component map
+
+```
+skills/<name>/SKILL.md         Agent instructions (purpose, inputs, procedure, evidence rules)
+skills/<name>/references/*.md  Supporting reference material loaded only when relevant (progressive
+                                disclosure — not everything is in SKILL.md itself)
+skills/<name>/scripts/*.mjs    Deterministic helper logic specific to that skill
+scripts/lib/skills.mjs         Shared skill discovery/validation used by scripts/cli.mjs and tests
+scripts/cli.mjs                Thin CLI: list / validate / inventory / release-audit
+scripts/release-audit.mjs      Public-release confidentiality/secret safeguard
+templates/                     Blank, reusable templates for cross-skill artifacts
+examples/synthetic-inventory-system/   Fully fictional worked example end-to-end
+tests/                         node:test suite over the deterministic scripts and skill structure
+```
+
+## Why no graph database, vector database, or orchestration framework by default
+
+Part A/B of the project brief explicitly calls for starting with a lightweight structured
+representation and introducing heavier infrastructure only when a specific project's requirements
+justify it. This repository follows that rule for itself: the knowledge model is plain JSON records
+(`docs/KNOWLEDGE_MODEL.md`), and `enterprise-ai-integration-planner` applies the same anti-
+overengineering rule when planning for the *target* project
+(`skills/enterprise-ai-integration-planner/references/architecture-alternatives.md`).

package/docs/DOCUMENT_INGESTION.md

@@ -0,0 +1,40 @@
+# Document ingestion pipeline
+
+## Goal
+
+Turn an arbitrary folder of project documentation (and optionally source code) into a structured
+inventory and evidence index, without ever loading the whole corpus into a single model context
+window, and without ever claiming a format was extracted when it was only catalogued.
+
+## Pipeline stages
+
+1. **Enumerate** — walk the corpus, skip VCS/build directories and anything the project profile
+   excludes, record path/size/mtime/hash.
+2. **Classify** — determine format by extension, falling back to content sniffing for ambiguous
+   extensions. See `SUPPORTED_FORMATS.md` for the authoritative support matrix.
+3. **Extract** — run the format-appropriate extractor. Preserve heading hierarchy, page/slide
+   numbers, tables, and links. Redact secret-shaped strings before persisting.
+4. **Classify extraction status honestly** — `extracted-full`, `extracted-partial`,
+   `unsupported-format`, or `extraction-failed`. Never upgrade a status beyond what actually
+   happened.
+5. **Index evidence** — assign a stable `source_location` to every extracted unit (see
+   `EVIDENCE_AND_PROVENANCE.md`).
+6. **Persist incrementally** — write results per file/batch to a private working directory (never
+   into this repository's public folders), so very large corpora do not need to fit in context at
+   once.
+7. **Summarize** — produce `INVENTORY_SUMMARY.md` with counts by status/format and a list of files
+   needing manual/visual review.
+
+## Reference implementation
+
+`skills/project-documentation-discovery/scripts/inventory.mjs` implements stages 1-6 for the formats
+marked "Verified" in `SUPPORTED_FORMATS.md`, using only Node.js built-ins. It is intentionally
+conservative: anything it cannot genuinely parse is reported as `unsupported-format`, not silently
+skipped or falsely marked extracted.
+
+## Incremental processing note
+
+For very large corpora, call the inventory function per-subdirectory or per-batch and merge results,
+rather than attempting a single pass that must hold the entire corpus's extracted text in memory or
+in a single prompt. The reference script's `runInventory()` function accepts a path and can be
+invoked repeatedly against subsets of a larger tree.

package/docs/EVALUATION_GUIDE.md

@@ -0,0 +1,36 @@
+# Evaluation guide
+
+## What can be checked deterministically
+
+- Skill structure validity (`node scripts/cli.mjs validate`).
+- Feasibility score arithmetic and blocker enforcement (`scripts/lib` + tests).
+- Presentation rule compliance for properties the deck format actually exposes.
+- Markdown/HTML structural well-formedness.
+- Presence of secret-shaped values / local paths pre-release.
+
+## What requires human or AI-assisted review
+
+- Whether a reconstructed architecture diagram is actually accurate (requires a human familiar with
+  the real system, or a second independent pass with code access).
+- Whether a drafted document/slide's prose is clear, well-organized, and free of subtly incorrect
+  paraphrasing of cited evidence.
+- Visual/aesthetic presentation quality (balance, diagram clarity) — flagged by
+  `presentation-compliance-validator` as `humanReviewOnly`, never auto-passed.
+- Whether an AI feature recommendation's business-value score is realistic for the actual
+  organization (the scoring framework structures the judgment; it does not replace it).
+
+## Suggested evaluation loop for a real project
+
+1. Run discovery + reverse engineering; have a human familiar with the project spot-check a sample
+   of extracted facts against the real system.
+2. Run the AI integration planner; have the data owner and a security reviewer check the opportunity
+   matrix's data-availability and security-risk fields before any pilot starts.
+3. For a shipped pilot, measure the metrics defined in the pilot's own `AI_EVALUATION_FRAMEWORK.md`
+   output against the baseline recorded before the pilot — never declare success without a measured
+   baseline comparison.
+
+## Never do this
+
+- Never treat "the model's output looked plausible" as evidence of correctness.
+- Never skip the human spot-check step because the automated structural checks passed — structural
+  validity and factual/business correctness are different things.

package/docs/EVIDENCE_AND_PROVENANCE.md

@@ -0,0 +1,40 @@
+# Evidence and provenance model
+
+Every fact this toolkit's skills state about a target project must be traceable to a
+`source_location`, or explicitly labeled as inference/unverified.
+
+## Evidence record shape
+
+```json
+{
+  "source_path": "relative/path/within/corpus.md",
+  "source_location": "relative/path/within/corpus.md#heading-slug",
+  "heading_path": "Human-readable heading text",
+  "evidence_type": "text | table | structured-data | code | image-caption",
+  "level": 2,
+  "extracted_at": "ISO-8601 timestamp"
+}
+```
+
+## source_location conventions
+
+| Source type | Convention | Example |
+|---|---|---|
+| Markdown/HTML heading | `path#heading-slug` | `handbook/lifecycle.md#archiving` |
+| PDF page | `path#page-N` | `spec.pdf#page-12` |
+| PPTX/Keynote-exported slide | `path#slide-N` | `deck.pptx#slide-7` |
+| CSV/table row | `path#row-N` | `data.csv#row-42` |
+| Source code | `path#Lstart-Lend` | `src/billing.ts#L120-L135` |
+
+## Confidence labels
+
+See `skills/project-knowledge-assistant/references/confidence-levels.md`:
+`documented`, `verified-in-code`, `inferred`, `unverified-claim`, `superseded`.
+
+## Non-negotiable rules
+
+- Never fabricate a `source_location`.
+- Never upgrade an inference to `documented`.
+- Always preserve both sides of a contradiction rather than silently picking a winner.
+- Treat superseded information as historically relevant, not simply deleted — keep the citation and
+  mark it superseded.